Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

We are developing a iOS shopping cart application in c# and visual studio 2017 for xamarin. I have an iPad Air iOS 10.3, when I try to publish to real device, I am getting the following error message: "Could not find any available provisioning profiles for iOS", I have tried to restart my Mac - without result. Give me any suggestion to resolve this issue?

You have an Apple Developer account and created the Provisioning profiles for your app? Also, did you downloaded the provisioning profile you created to the Mac you're working on? pinedax Apr 10, 2018 at 18:11

In Visual Studio for OSX, go to Visual Studio Community > Preferences > Publishing > Apple Developer Account and click to + button to sign in and add your developer account. In theory after that automatic provisioning should work.

In Visual Studio for Windows, go to Tools > Options > Xamarin > Apple Accounts , you will get a prompt to install FastLane before your Apple ID will show up under Automatic Provisioning.

You must create a provisioning profile. Search on Google, how to do it.

But, the secret is: when you create a provisioning profile, you must associate an App ID to this profile, like: "com.companyname.*" .

When you create your app in visual studio, you must set in the INFO.PLIST file on IOS PROJECT, the Bundle Identifier to "com.companyname.myapp1" or anything else. If your Bundle Identifier has a name like "com.myapp.app1", you will get this error: Could not find any available provisioning profiles for iOS , because your profile accept only apps with the names started with com.companyname and you are using a appname different.

I dont know why your suggestion got down-voted but it is correct. I did same and it works for me. pixel Aug 8, 2018 at 21:19

For those who just want to deploy/test their app on a real device with "Free provisionning" follow this official guide .

To sum it up :

  • Create an apple id
  • Add the previously created apple id to XCode in order to add a provisioning profile.
  • Create a new empty iOS app with the bundle identifier equals to the one of your Xamarin app (you can find it in Info.plist of your Xamarin.iOS project).
  • Ensure that your empty iOS app could be deployed, by running it from XCode on your device with your free provisioning profile.
  • In Visual Studio open Info.plist and click on Bundle Signing Options... , in Signing identity chose Developper automatic and Automatic in Provisioning profile .
  • Run your Xamarin.iOS app on your device.
  • You can see what was wrong with your provisioning profile in xCode. Also this procedure will update Provisioning profiles, Certificates, App Ids:

  • Go to xCode, create blank iOS application, type the same Bundle Identifier, that you had in Visual Studio.

  • On the same page uncheck "Automatically manage signing".

  • In Signing (Debug) click on Provisioning profile. You will see Eligible and Ineligible provisioning profiles. You can select each of them and if one is Ineligible, then errors will be shown below. After that you can fix them.
  • After that you can go to Visual Studio for Mac and create the same project with the same bundle id and check you profile in Project -> Options -> iOS Bundle Signing -> Provisioning profile
  • After that you will find your Provisioning profile in Visual Studio on Windows
  • I suggest you read this documentation to learn more about iOS provisioning.

    What you want is called automatic provisioning though. It takes care of all the complex things about provisioning for you and just deploys the app.

    Visual Studio on Windows has the automatic provisioning feature in preview (called 15.7) right now (preview 3): https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-preview-relnotes#xamarin-provisioning .
    I recommend you try that, it should help you automatically add your iPad to the relevant provisioning profile.

    Visual Studio for Mac has had automatic provisioning for a couple releases now.

    Note: you do need an Apple Developer account to deploy on device (it can be a free developer account).

    As of July 2018 Visual Studio for Windows doesn't do automatic provisioning for iOS devices Gerry Jul 12, 2018 at 21:29

    Unbelievable but true...

    To enable the interface, I first had to login with my Apple account under:
    https://itunesconnect.apple.com
    https://appleid.apple.com
    and agree the new privacy agreement from Apple. There isn't any error message that points you in this direction ("you first have to agree...").

    After doing that, I was able to use the automatic provisioning in VS2017 and connect to the Mac.

    No help to me, I followed same you stated but in VS for Mac IOS Bundle Signing, I see Provisioning Profile dropdown being disabled pixel Aug 8, 2018 at 20:52

    All of these answers are right.

    There are many reasons the creation of the provisioning profile certs bundle can fail. The one I dont see listed here is referenced in ( Apple developer account teams not showing up on VS Mac )

    Only XCode can set up the provisioning for you using the free apple dev Id. You need to create a dummy project with the same Bundle Name and Bundle Identifier. Build it in XCode and have XCode create the certs for you.

    Only once i did that (on the paired Mac) did it start actually building my iOS target in Windows VS 2017

    First background

    I have already provisioning profile for app we are building but every once in a while I have to create a small POC app to prove something. And often I have to use that small app on real provisioned device.

    But I was not even able to see my device for that small POC app in the dropdown showing available devices. Only the app I am building with my team will show.

    Solution

    To resolve this, I had to do

  • In my POC app > Info.plist, make sure your Bundle Identifier is same as for the app that you can deploy to your device
  • At the same location, under Signing, select "Automatic Provisioning" and you should see your Apple ID show. In Team dropdown, select your team
  • After this, my device showed, I was able to build and deploy to it and the error was gone.

    I have tried all the above-mentioned approaches but didn't work. I was using Manual provisioning.

    To identify why it's not showing in VS, I have:

  • Opened the Xamarin.ios project in Xcode.
  • Under Settings > Manual provisioning profile,> Selected the appropriate certificate (Note: It should be installed before it appears in the list).
  • It showed me an error, which said "Selected provisioning doesn't match with the distribution certificate in the keychain"
  • When I logged into developer.apple.com - I have found a new distribution certificate.
  • I had to regenerate the provisioning profile with the new distribution certificate (selected) and installed it.
  • After installing the error went away.
  • Also, In the Visual Studio's drop-down list the provisioning profile started to appear.
  • I agree with Meekohi & Vincent Dondain who have recommended choosing Automatic Provisioning, as it's a better option if one is not facing any issues with certifications or profiles as it takes care of everything. However, using the latest Visual Studio for Mac is preferable.

    just hit the same problem. didn't find solution in this thread that i came to. Xamarin app, visual studio for mac . manual signing

    didn't use it for few months. works good on emulator but can't deploy to device for debugging

    after reading this thread went to developer.apple.com and found, that my developer profile expired a month ago.

  • create new provisioning profile
  • visual studio for mac-preferences-apple developers account-details-download manual profiles
  • info.plist-bundle signing options-choose correct identity and profile
  • Answer ( I have had this issue 2 times by switching MACS & adding new applciations )

    Issue: Profile not showing up in dropdown below ( Automatic Distribution or Distribution )

    As long as you are sure your info.plist is ok and have matching ( com.companyname.something ) & your CERTS are in Keychain then this is what is what cleared it up for me 2 TIMES !

    ** This seems to be some sort of refresh issue ( where a old profile is cached OR newer profile/bundle not loading in MAC )

    [ I use VS on Windows and connect to MAC ]

  • Open Visual Studio for MAC ( not windows )
  • Create a new ( blank form ) iOS project
  • Click Visual Studio in Menu and Click Preferences
  • Click Apple Developer Accounts ( ADD YOUR APPLE ACCOUNT )
  • CLICK VIEW DETAILS & DOWNLOAD ALL PROFILES & Close
  • Open info.plist in your Folder View in VS
  • Check Manual Provisioning & Type in bundle Identifier com.companyname.whatever & App name
  • RUN BLANK APP & CLOSE IT 10 ********* Go back to Windows right click on iOS Project Select Distribution AND YOUR BUNDLE IS IN THE DROP DOWN !!
  • [ If bundle not there re-connect to MAC right click and see if its there in your dropdown - remember the bundle must be in your iOS project ( root ) ]

    ( Automatic distribution will work as your bundle will be in the dropdown below in Windows Visual Studio & RELEASE TO APP STORE ).

    One of the reason could be that there is no Provision profile file

    For MAC the path is /Users/apple/Library/MobileDevice/Provisioning Profiles

    You need to download the corresponding provision file from apple developer account and then paste it here in the above directory

    Then, it will start reflecting in Visual Studio

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question . Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers .