I have implemented the Push Provisioning API using Google Tap and pay client.
While querying linking token I am facing the below exception.
W/System.err: com.google.android.gms.common.api.ApiException: 15009: Calling package not verified
I have tried to create signed apk and install, but still same issue
Anybody help me out to unblock me?
that error occurs when you don't have access to push provisioning API.
You can see it on the troubleshooting page:
https://developers.google.com/pay/issuers/apis/push-provisioning/android/support/troubleshooting?authuser=1
To solve this you need to ask access for Push Provisioning API. Google has to identify your application as well as its version(production, development, debug). Versions as you know are differentiated by the key that signs them. Generate the correct version of your app gets its SHA 256 fingerprint and provide it in the aforementioned form.
Here are the instructions:
https://developers.google.com/pay/issuers/apis/push-provisioning/android/allowlist?authuser=1
Key used to sing your app on the Play Store maybe different than the one you use locally to generate signed apps. Also Debug versions take the default key from .android directory(you can find other stack overflow posts that provide information about debug keys and their credentials.)
Related
I received a Hololens 2 that was previously used by someone else. Their account is currently signed in so I have been trying to factory reset it following this guide provided by Microsoft here. However, when I trying to follow the "Clean-Reflash" section it requires me to be signed in to perform the reset. This results in a chicken or the egg problem as I don't have access to the signed in account, but I am unable to reset the device to log into a new one. Are there any other reset options?
Permission denied when trying to reinstall software
Resolved. You need to do a manual installation instead of a normal one as in the documentation.
I'm using SHA1 debugging key in firebase for debugging my application, but I want to release my app in the play store where I'm providing Google authentication in my application.
What can I do for release mode where do I get SHA1 release mode certificate and what can I do with that?
Is it necessary to download the json file again? How can I do that?
I had the same problem and found this enter link description here
Basiclly what he did, and for me works fine, is one you upload the app to google play:
Go to Release Management
Select App Signing
Use the SHA1 that you see there in FireBase
Revisiting a project I've not opened for a month or so I've found that the sandbox account I previously set up cant be accessed, visiting;
http://admin.wechat.com/debug/cgi-bin/sandbox?t=sandbox/login
Allows me to log in via. the scanning of the QR code but after (seemingly) managing to log in it then gives the error 'Unable to initialize'
Previously this worked I'm wondering if there's been an unpublicised change to the WeChat platform?
So I've not been able to figure out if/why the wechat.com sandbox service has stopped working and if I'm an isolated case or it is a common problem
I did discover that the Weixin sandbox service on https://mp.weixin.qq.com/debug/cgi-bin/sandbox allows me to log in / access the same test app tied to my WeChat account so for others having issues the answer may be to use;
https://mp.weixin.qq.com/debug/cgi-bin/sandbox?t=sandbox/login
Same here! The International sandbox is not letting me in, but the Weixin one works.
Unfortunately in Windows store 8.1 there is no API available to extract or create a archive with password ,at least this what i find out after a lot of recherche on the web,
And because this is very important for us to find out something, we created a package on nuget.org that works like magic. Basically we manage to create/extract archive with password but sadly this does not pass the certification Kit evaluation.
http://www.nuget.org/packages/DotNetZipforWindows8.1/
I wonder if anyone can help us to get this API pass the test.
this is what i get in the certification Kit evaluation
http://social.msdn.microsoft.com/Forums/getfile/465599
I've already asked similar question on this issue on stack overflow already, but I believe this part of the issue can be separated into a new question.
I've not done mobile development before so the use of signing and certificates is a new concept to me, and for all the reading of topics I have done, its not really improved my knowledge as each website I read talks only about a small part of signing, not the complete process, and piecing it all together has been difficult.
The issue I have is my driver is not been loaded at startup on WM6.1. Its a driver for GPS so needs to be loaded so its available to any GPS software accessible on a COM port. I believe this is due to a signing issue, given that the DllMain method is never called.
I have been given a privileged certificate (.pfx) to use, and for the record have also got the new (Jan 2010) SDKSamplePrivDeveloper certificate as well. I assume a privileged certificate is needed for drivers.
So what have I actually done. I've tried atleast several variations on this over the last 4-5 days all with no success.
In visual studio;
1)The DLL project has authenticode signing set to our .pfx certificate. Build the project.
2)The CABWizard project has authenticode set to the same certificate. Build the project.
3)Following the MSDN instructions... Converted the .pfx into a 509 Base64 Certificate, and created an XML provisioning file from it.. It has been created into its own CAB Or CPF file. And also tried provisioning the _setup.xml file into the previously created CAB file so its installed with the application.
4)I have installed these onto the device, and whilst the driver does work in our test app it does not load at boot even though its registry settings in "BuiltIn" are correct. When checking the certificate stores in the registry I can see the certificate added to the SPC, Root, Privileged and Unprivileged stores. And when using System|Certificates I can see the certificate in Root tab. So they have definitely been added.
Given the above did not work. I have also tried the siggner.exe tool from http://www.modaco.com/content/i8000-verizon-sch-i920-omnia-ii-http-i8000-modaco-com/306870/sdkcerts-2010-and-signing-tool/ with the SDKSamplePrivDeveloper certificate.
1)The Dll project has authenticode signing set to No. Build the project.
2)Load up siggner.exe and sign the Dll file with SDKSamplePrivDeveloper.cer.
3)The CABWizard project has authenticode set to No. Build the project.
4)Load up siggner.exe and sign the cab file with SDKSamplePrivDeveloper.cer.
5) Use NewSDKCerts.Cab to install the SDKSamplePrivDeveloper certificate into the stores.
6) Install the CAB file i created with the driver.
7) Again, on a warm reboot the driver is not loaded at boot into device.exe.
Given the above, can anyone give me some clear instructions on a sure fire way to load the driver at startup. I'm obviously doing something wrong with the signing given this does boot up without an issue in Windows CE5. I know the device driver code is OK as I can activate it manually in code with ActiviateDevice() method in WM6.1.
Edit--
It maybe worth adding, I also created a DLL and CAB with no signing at all. And on a clean boot of the OS it installed without complaining. Whilst still not loading at boot I did expect warnings about the CAB and DLL been unsigned.
The reason for driver failure, was not a certificate issue.
The driver was originally self contained and also contained some GUI code, and has since expanded. A library used to make the application full-screen was not available at start up so it silently failed with a dependency issue.
This has currently been resolved with a start-up application loading later to wake up the driver, once the library is available. A proper solution to be added is late loading of the required library to prevent a dependency failure.
Driver signing was also an issue in a related matter with this driver. We now have a certificate from the manufacturer to sign drivers so that issue was resolved as well.