I am using a macbook pro with visual studio community.
The error I receive in the console is:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(644,3): error : Could not find any available provisioning profiles for iOS.
I noticed that this error came up once we added the SecureStorage plugin to the project. Any commit prior doesn't result in this error.
Screenshot From description above
Gone into project.ios >> Info.Plist and checked that the bundle identifier and application name is correct. Screenshot from info.plist
Enabled KeyChain access: project.iOS >> Entitlements.plist >> KeyChain >> Enabled KeyChain ticked >> KeyChain Groups >> Added correct keychain
KeyChain Enabled
Then when I go into project.ios >> Info.Plist >> ios Bundle Signing >>
iOS Bundle Signing >> Provisioning Profile
It can't see any matching profiles. See screenshot
This problem was tricky to solve for a few reasons:
I did something similar to what's demonstrated here: https://www.youtube.com/watch?v=S9lNmnyACpY
Open up xCode and create a new project (can also do this under the apple developer page) and create a new project with the same namespace (eg: xfPOC in my case) as your xamarin forms project.
Copy the provisioning profile name it creates and then paste it into your "bundle identifier" in info.plist. From there, go into ios bundle signing and it should be able to find your provisioning profile.
My aplogies to @SushiHangover who was actually correct, I originally replied to him saying that my bundle identifier did match my provisioning profile(which at the time didn't exist). By "provisioning profile", I thought that was set up at the beginning of the xamarin forms project as the organization Identifier, this is confusing because VS copies that into the bundle identifier in info.plist, which isn't particularly helpful because it looks like it's set everything up for you, whereas you need to go and create it yourself in xcode or on the apple development page. Personally, when I did that in my project, the provisioning profile did not match the default bundle identifier that VS created.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With