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.)
I have a few multi-tenant application on AAD App which requests access to Mail, Calendar, Contacts and Tasks . The apps works successfully for a few years without any issue, but last few days started to get error :
"AADSTS650051: Application 'CLIENT_ID' is requesting permissions that are either invalid or out of date"
All of them !!! Without anything that changed in apps permissions settings. So, new domains can't now install those apps.
Remove app from the installed domain and install it again, doesn't helps.
Please advise.
Thanks
Well, found an issue - two permissions, one of them is Deprecated_ThreatIntelligence.Read, was not able to remove it, when tried to remove got ok, but permission was there again. After talking with MS support (paid support, after 48 hours of phone and email conversations) got nothing from them expect :
I would like to inform you that I have reached out to my peer
engineers with all this information and waiting for their suggestion
to proceed with further investigation on it.
I would request you to allow me sometime so that I can discuss with my
peer engineers and get back to you with an update on it.
Had no choice and needed to solve this quick as possible, found a way to remove , downloaded manifest (it'a app configuration JSON), removed problematic permission (not an easy task, as there's only guids) and uploaded manifest again. Issue solved.
Shame on microsoft support !!!! One of the useless paid support I ever saw. Can't do anything except waiting for feedback from engineers. This issue supposed to be fixed by support within 5-10 minutes, once they have request id and correlation id, but they didn't find a solution up till now. And shame on Microsoft, lost customers for last 10 days, due to their weird bugs.
The problem is exactly as described in the error message. Credentials for your app has expired.
Go to Azure AD -> App registration -> Your app -> Create new key
This deprecation warning has been in the documentation for a while. The removal of the scope just happened within last couple months.
https://learn.microsoft.com/en-us/office/office-365-management-api/get-started-with-office-365-management-apis#specify-the-permissions-your-app-requires-to-access-the-office-365-management-apis
Paragraph 3.
I develop an Azure DevOps extension. Now I want to automate the publishing process. Here the journey begins ... Following the theory here the reality looks different to me.
For me every trial of publish via command line ends in
tfx extension publish --auth-type pat -t
7dblablablablablablablablazq --share-with examplecompany0123
TFS Cross Platform Command Line Interface v0.6.3
Copyright Microsoft Corporation
Checking if this extension is already published
It isn't, create a new extension.
error: Received response 401 (Not Authorized). Check that your personal
access token is correct and hasn't expired.
My first guess on that error message 401 was that I probably have a wrong PAT. A look in my PAT management showed me that everything seems good.
So, now I am confronted like a cow at a five-barred gate. I just don't get the root of the failure. Anyone here who already has left this noob beginner problems behind and reached the next level and can help me?
Ensure your PAT have Account: 'All accessible organizations'.
This just started happening today after I got a message from xcode to agree to new t&c's.
I can't put anything on the device, on any of my computers.
Doesn't work on my macbook, doesn't work on my mac mini, doens't work with existing projects that worked fine until yesterday, doesn't even work with completely new projects.
I constantly get the message:
writeDictToFile:1241 open failed for
/Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist
: No such file or directory MDMCacheDirectoryManifest:1315
writeDictToFile failed to write to
/Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist
: No such file or directory error MT1006: Could not install the
application
'/Users/georgecook/Desktop/test/iOS/bin/iPhone/Debug/test.iOS.app' on
the device Gandalf the white: Your application failed code-signing
checks. Check your certificates, provisioning profiles, and bundle
ids. Probably your device is not part of the selected provisioning
profile (error: 0xe8008015).
No idea why this is suddenly happening - this is really not good - how to resolve this?
I tripped over this one recently too.
The key is this part of the message:
Your application failed code-signing checks. Check your certificates, provisioning profiles, and bundle ids. Probably your device is not part of the selected provisioning profile
Likely, your provisioning profile has expired. The easiest way to solve this is to launch Xcode, create an empty project, and hit Run. This will go over a series of dialog boxes offering you to fix your provisioning profile until it deploys. Once this happens, you can switch back to Visual Studio/Xamarin Studio and deploy.
One reason this can happen is if you have multiple developer accounts set up in XCode. Here are the steps
Verify that your device is on Apple member center
Verify that your device is part of the relevant provisioning profile
Repeat steps 1 and 2 for each account
Create a new project in XCode and run it on the device. XCode may ask you to select the team (if you have multiple accounts)
If you have multiple developer accounts (teams) set up in XCode, the repeat step 4 each time with a new project and select a different team each time.
These steps ensure that XCode clears the way for Xamarin. The idea is that Xamarin does not allow you to decide which "team" to use, so you want to make sure that XCode has done the setup for EVERY team.
I just had this ManifestCache.plist : No such file or directory problem. I checked device logs (View -> Pads -> iOS Device Log) to see why it was happening. Logs said it was rejecting an upgrade. Upgrade, I thought to myself, that doesn't sound right...then I remembered I had an app on my iPhone with the same identifier to.dima.application from a previous version which I forgot to uninstall. Removing the old app cleared up this issue for me. Hope this helps anyone else who has the same problem! :)
It works! I have found the solution.I was facing the same problem. Somehow there was a misconfiguration in Xamarin. The entitlements.plist had a wrong manuel entry. The cert ist checking all the values in it and if you have a manuel entry there it is not working anymore. Apple is searching somehow only for own entry they are needing.
I spent sometime on developer portal to find out the problem, it occurs because of distribution APNS or development. It did not fixed, after restoring all provisioning profiles and certificates, . In my case solution was letting Xamarin choose signing profiles. I did not use info.plist auto signing which did not solve either but changing Project -> iOS Bundle Signing -> Signing identity, Provisioning Profile Auto solved all issues for development and production cases.
I had the same issue, and so I opened Xcode and updated all my profiles, but nothing happened. So I added the device UDID in the developer portal to the team I was developing for, went to Xcode and updated the profiles again, and then it worked. Don't know if the device must be registered to be able to build to device or this triggered some other update to my profiles that suddenly made it work.
Today they published a new revision of the Apple Developer Licence agreement.
The error message was essentially the same as OP's. The true reason only became apparent when creating a new project in XCode on the Mac, where more useful warnings show up in the "Deployment info" section of the "General" tab.
I had to log in to apple.developer.com, there was a red panel asking me to accept the new licence conditions, and as soon as I did that, deploying apps from Xamarin immediately worked again.
I had to recreate my Windows user profile due to some technical problem that kept me from logging in. Now I'm trying to recover all my software, etc. I start VS2012 and opened the project I'm currently working on which is an SSDT/SSDT-BI project - database model and an SSIS project. I'm getting the following error:
Warning 1 Warning loading ADSMetricsETL.dtproj: Warning: Failed to decrypt an encrypted XML node. Verify that the project was created by the same user. Project load will attempt to continue without the encrypted information. ADSMetricsETL.dtproj 0 0
So I suspect there's a GUID or SID somewhere that identifies me as the owner of the SSIS packages and it's got my original profile's values stored identifying the "old me" as the owner. Is there any way to easily change ownership to my new profile?
For completeness sake I'll add my comments as an answer:
Change the protection level to DontSaveSensitive. This warning usually comes up when sharing packages between different users since the default protection level is EncryptSensitiveWithUserKey.
I'm glad that you do not have any sensitive information in the package -- it always best to use parameters or configurations.