Device UDID is already present in my developer account still getting the error as waiting for developer in firebase and fastlane - ios

I am trying to build the app and upload to firebase through fastlane.
Add distributed successfully, but after the distribution the app shows the Waiting for developer and need to add the UDID.
But already I have added that UDId of the user in my provisioning profiles?
How this will be happen?

Not fully understanding the context here but whenever I ran in a similar issue I need to archive the build once again making sure it gets the updated provisioning profile.
Also, if you use SIGH and you want all your devices being added automatically, every build I recommend using force option.
http://docs.fastlane.tools/actions/sigh/#parameters

For firebase distribution using the fastlane, I need to set the adhoc certificate. The above issue got because I have distributed the app using AppStore provisioning profile.
Added the export_method as Adhoc and run the build it get succeeded and able to install the app on my phone.

Related

Xamarin iOS release automatic provisioning - none of the currency installed provisioning profile

I have read and tried all the fixed associated with releasing and app to the App Store, but I cannot find any suitable fix. I have setup an iOS developer account and created account, I have setup Xamarin to automatic provisioning but I am getting the error message "none of the currency installed provisioning profile". I have tried the following
Upgrade Xamarin and X Code
Change all Bundle Identifiers to the same
Delete all the certificates from the KeyChain
Restarted MacBook
Switched from Manual to Automatic bundles
Created a test app
Removed certificates from iOS account
Rebuild, cleaned, achieved the project several times
I just cannot resolve this problem, any help would be highly appreciated as it's driving me around the bend to release the app into the App Store.
Many thanks
You should use manual provisioning instead of automatic provisioning when releasing your app to app store.
From the official document about publishing iOS app to App Store:
https://learn.microsoft.com/en-us/xamarin/ios/deploy-test/app-distribution/app-store-distribution/publishing-to-the-app-store
In the release build steps:
Navigate to the iOS Bundle Signing tab. Make sure that Configuration
is set to Release, Platform is set to iPhone, and that Manual
Provisioning is selected.
Of course you will need to have the corresponding distribution certificate and distribution provisioning profile created in Apple Developer page.
Many thanks for the help, I managed to resolve the problem with the following setups
Update all packages
Removed x-works (it was the latest version any way)
Re-install x-works
Delete all relating certificates in Keychain
Delete any certificates, profiles etc in app development site
Re-start Xamarin and MacBook (in the end did this several times)
Log out of Apple account in Xamarin
Re-log back into the Apple account in Xamarin
Setup auto provisioning in Xamarin i..e dev, dist etc and created the appropriate certificates
Generate a certificate within keychain using iOS account details
Plugged in iPhone and rebuilt the complete project
Achieved the build
Now it connected to the App Store and released the app
I am pretty sure you don't need to do all these steps, but seems like it took it back to the start of setting up Xamarin for app releasing. One problem might have been multiple certificates in KeyChain which caused the problem.
Many thanks for all the help and support.

Appcenter iOS install error "this app cannot be installed because its integrity could not be verified"

I see that this question has been asked many times but I see no solution that works for me so I'm hoping that providing more info might shed some light.
We use appcenter.ms to test iOS apps. Until our iOS certificate expired this method worked fine. We generated a new enterprise certificate and ad hoc provisioning profile for new releases of the iOS app. Which led to the first curiosity.
I see how to upload a certificate on appcenter.ms but not a provisioning profile. I thought there was an option to do this in the past but perhaps I am mistaken. However, the app is signed with a provisioning profile before upload, so perhaps this is not needed now.
Once the app is uploaded, it can't be installed. It remains grey and when you tap it, you get the "this app cannot be installed because its integrity could not be verified" error. Again, that the .ipa is created with an ad hoc certificate and profile in Xamarin (VS for Mac).
Also, I can't install the provisioning profile on a device from appcenter.ms. You basically get stuck in a loop where you seem to successfully install the profile but have to keep doing it because it never actually installs.
I hope this is enough info for some insight and thanks in advance for any feedback.
We were able to solve this by redoing and downloading development certs and via
And also downloading and double clicking the apple development certificate here
After that our keychain showed both as trusted and we could build to the iPhone again.
The issue can be the your device is simply not registered on the developer portal and/or that ad-hoc provisioning profiles have not been regenerated.
You need to register your device, regenerate a provisioning profile with this device in it and rebuild your app using this profile.
This can also happen because of
Developer ID Notary Service - Outage
which can be checked on https://developer.apple.com/system-status/
Notarization is well explained here:
Notarization gives users more confidence that the Developer ID-signed
software you distribute has been checked by Apple for malicious
components. Notarization is not App Review. The Apple notary service
is an automated system that scans your software for malicious content,
checks for code-signing issues, and returns the results to you
quickly. If there are no issues, the notary service generates a ticket
for you to staple to your software.
Work around fix:
Select your app.
Navigate to TextFlight tab
Create External Testing group
Add one tester
Add build which you want to download using TestFlight
Open TestFlight and download an app.
In my case this was caused by trying to include an entitlement for aps-environment "development" when using an Ad-Hoc provisioning profile. The value for this environment in Entitlements.plist must match what is hard coded into the provisioning profile file - if you open an Ad-Hoc profile in a text editor you will see it expects the "production" environment.
The possible solutions depending on your requirements are to either use the Development profile/certificate, or change the aps-environment to "production" to continue using an Ad-Hoc provisioning profile.
It can also happen if you have other incorrect entitlements - worth checking what entitlements are enabled under the Identifier in Apple Developer portal and removing unnecessary ones.
I had this issue because when building the app on xCode for distribution (Product->Archive then Distribute App), I chose automatic signing. After manually signing the app and choosing my own generated certificate and profile, everything worked again fine.
I removed the Entitlements file from the Addition Resources in iOS Bundle Signing and it worked.
I think the MSAL configuration was set to debug in entitlements.plist
I have also face this issue before but for me the reason was little different
First the build was enterprise one and the build was made on the earlier Xcode version on which the iOS version you are using on the device was not supported by the Xcode.
All I did was to update my Xcode and make a new build and shared the build. After that we were able to install that build over device Hope it works for you as well
This is how I solved for myself.
In you iPhone Settings > General > VPN & Device Management you should see your company name (if an app from it is installed), and if you click on it, you will see a button like "Verify" above the list of apps installed provided by the company. Just click on "Verify".

iOS how to add a provisioning profile

I am using Xcode Version 8.3.3 (8E3004b). I have an app developed that I would like to deploy to Apple's App Store.
In order to Archive and deploy, I understand I first need a provisioning profile. So, in the developer console, I set up an iOS Distribution Provisioning Profile.
I also have the following certificates:
On my MacBook, I added the following certificates to the key chain:
Then when I go to Xcode, I would expect to have a Provisioning Profile:
But as you can see, it Failed to create provisioning profile and No profiles for 'com.ionicframework.thewhozoo912107' were found.
I am obviously missing some step in order to create the Provisioning Profile in order to distribute the app to the Apple App Store.
Question
If anyone can suggest what I need to do in order to create a working provisioning profile in order to distribute the app, I would appreciate the help.
More info:
Solution:
I fixed this in Xcode by unchecking Automatically Manage Signing, and then selecting my provisioning profile.
I had that problem as well when I was developing my first app. It took a while, since I managed it. Try to plug your iOS device in your computer and then it should work.

Fabric/Fastlane - Automatically Add Device UDIDs

I'm using Fabric and Fastlane to deploy my beta builds to testers. Currently, when I have a new tester, I invite them via email, and they go through the Fabric onboarding process. Then, on all future builds, they'll receive a message "The developer needs to add the device's UDID to a build." So then I go to developer.apple.com and add their UDID to my provisioning profile, and they can run the next build. It works as desired.
Is there any way within Fabric/Fastlane to automate this process of adding UDIDs to the provisioning profile on deployment? It seems sigh within Fastlane can manage provisioning profiles, and Fabric obviously has access to the device UDIDs, but I can't find any documentation about this particular step.
Check out the docs on how you can use fastlane to automatically add device testers to your profile: https://docs.fastlane.tools/getting-started/ios/beta-deployment/#best-practices
There is currently no automatic integration with Fabric Beta, you'll have to manually add it to your list of devices. It's definitely something that can be improved.

Device Anywhere - App may not be signed

I am building my application using XCode 6 and App Store provisioning profile. After creating the application, I tried to upload it in Device Anywhere (Keynote), but it is giving me an error saying the app might be unsigned and that I need to sign it. I also tried it with AdHoc profile, but it is the same.
To verify, I installed the application on my test device, the one signed with AdHoc and it is working properly. I also verified the IPAs with security cms command and the IPA are getting generated properly.
Any help regarding this will be helpful.
Is the device in which you are trying to deploy the code, registered under the same provisioning profile you are trying ? Please check on this.
A provisioning profile binds
Certificate
App ID
Device UDID.
So basically only if your device is under this particular provisioning profile, you will be able to deploy.
The issue has been resolved. Build the application using AdHoc profile and during upload selection the option to re-sign it. Also using Device Anywhere version 7.0 or the latest one. That will resolve the issue.

Resources