I am trying to run previously code signed app source code on an iOS device using xamarin studio.
Since I have to code sign it with the new identity for my device.
where should i add the code sign stuff in xamarin studio.
well....
in xcode i could do this under the "build setting->code signing" section.
but xamarin doesn't have this kinda stuff inside, i guess
I have already added my Apple Dev. Account in Xamarin Preferences. and included in in info.plist under the "Team" section.
but nothing seems to work..
When i run the app i.e debug the app on an iPad
it still asks for the previous code sign identity.
what am i missing ?
or
is it not possible to code sign a previously code signed app with a different identity in xamarin studio. ?
PS. :- i am using xamarin studio version 4.2.2
EDIT in favor of binncheol answer
i don't think there is anything like "Option' > 'iOS Build Setting"
have a look at my screen shot of the tool bar.
also..
if you meant 'Options' by 'preferences'
here is screen shot of my preference window in xamarin.
If you go to the 'Options' > 'iOS Bundle Signing' menu for your iOS project in Xamarin Studio you should be able to select your identity and provisioning profiles.
Related
I have a Xamarin Forms app that was last published using Xamarin Studio in 2017. The app builds error free using Visual Studio 2017 and runs fine when an iPhone is connected to the Mac. When I try to publish it to the Apple store I get numerous
ERROR ITMS-90045: "Invalid Code Signing Entitlements" saying they are
not supported on iOS such as UILaunchStoryboardName,
NSCameraUsageDescription, NSPhotoLibraryUsageDescription,
CFBundleIdentified, MinimumOSVersion, etc..
I created new certificates and profiles without success. There are no duplicate keys in Info.plist and the multiple Info.plist files in the IPA are all unique. All the keys that are in error can be found in Info.plist. The iOS Bundle Signing points to the new Provisioning Profile that I created. The certificates in the KeyChain have not expired.
Here are two screen shots of the Info.plist dropdown list of available properties. In my app I don't have the correct list 1. I'm assuming this is why it is erroring out. In a new test app 2, the list is correct.
I am new to Xamarin. I Have created a app and trying to integrate Push Notification in IOS. But When I try to add Apple Developer Account to Xamarin studio it gets added but when i click on 'View Details' it does not show me the Signing Identities and Provisioning Profiles.
But I Can view it in X-Code
First of all I advise you to install Visual Studio for Mac, it's the successor of Xamarin Studio, Xamarin Studio will no longer be maintained.
It's normal, Xamarin Studio does not support all the feature of Xcode, the compilation is based on Xcode so for certains actions you need to use Xcode, it's more clear and easy.
I have App ID and Provision Profile properly set. But Entitlements.plist file not able to find App ID. When I click on option in entitlements.plist file to enable, Below error displays.
Error is : "An App ID with identifier 'xxxx' is not available. Please enter different string."
I have tried with many different different identifier for iCloud and Data Protection option. but same error always.
Please help me since because of this I am not able to proceed with any entitlement in the Project.
I have latest Xamarin studio and all other component version till today.
Xamarin studio : 6.3 (build 863)
I have installed fastlane and Added Apple accounts to xamarin studio preference.
I have asked question in xamarin forum too. Link : https://forums.xamarin.com/discussion/comment/269581
I have the same problem, as I can see the only way to resolve it is change your bundle id string in info plist and recreate provision profiles.
I can't find any documentation on how to publish your app to the app store from Visual Studio? Is this a case of having to use Xamarin Studio once you are ready to submit your app?
It seems a bit odd that xamarin gives you the opportunity to use Visual Studio but then has absolutely no instructions on how to create a bundle to submit your app to the app store..
Any tips on how to do this with Visual Studio would be great.
As far as I know, there's no way of submitting to AppStore (or even TestFlight) from VS.
I believe that you can only submit builds to the App Store using Xcode or Application Loader. Both Mac programs.
Personally I make a release build in Visual Studio, and then click the 'Show IPA File In Build server' button.
If the buttons greyed out, right-click your iOS solution, select properties. Then go to 'iOS IPA Options' and check 'Build ad-hoc/enterprise package (IPA)'
Then I go to my Mac and start up Application Loader and drag the IPA file there.
I am using visual studio for Xamarin development and I have a business license for both Android and IOS. The Android version of my project is nearing completion and I want to begin development on the IOS version.
I am following the process listed in the requirements and installation section of the below link:
http://developer.xamarin.com/guides/ios/getting_started/installation/windows/introduction_to_xamarin_ios_for_visual_studio/
I have added my Apple Account ID to XCode however as far as I can tell you need to manually assign an IOS Certificate to the build hosts keychain to beable to build from visual studio
If you are using Visual Studio for Xamarin.iOS development, you also
have the option of provisioning manually using the Apple Developer
Portal.
Now as far as I can tell this has a $99 cost involved? Is this fee mandatory before I can build any IOS apps from visual studio ?
EDIT:
After pairing the build host and building my app it seems my suspicions are confirmed. A IOS Development Certificate
stored in the keychain is required
As far as i know you don't actually need the iOS Certificates for developing with Visual Studio and the build host, as long as you're running your app on the iOS simulator. However, as soon as you want to test your app on a real device you need the certificates. And just a reminder, you should test on real devices as soon as possible. I got some really bad surprises after developing exclusively on the simulator for more than 6 weeks ...