I am using Unity to build an Xcode project. I already implemented in-app purchase and added the StoreKit framework to the project.
But the "Capablities" settings in Xcode shows that the "In-App Purchase" toggle is off.
My purchase on sandbox does work. But I don't know what effect does this "In-App Purchase" button have.
Unity does not have an automatic way to set Capablities settings and I don't want to set it every time.
Should I turn it on?
Related
I noticed Xcode 12 has changed a lot new redesign interface so capability has no longer shows up the switch to enable or disable in Xcode 12. So can someone find the enable inside the IAP Capability to show up the checkmark to make sure enabled or not? I can't get shows up the IAP in my devices due to the needs that enable the IAP to checkmark in the Capability.
Let me know. :)
If already enabled, you should see it under the Signing & Capabilities Tab.
if you can't see it, then to enable IAP with your target selected,
Then search for in-app and select it.
i have several apps in the AppStore but now i am struggling with one of the apps submission.
I added to my app the chart module, and i used AMCharts for that, so to make it work, i added the AMChartLibrary project into my project, and everything works fine either usgin the simulator and the device itself for testing, and now I am ready to submit the new version to appstore and then the nightmare starts
When i run the archive to create the file to be submitted, it falls under Other Items instead iOS Apps, this disables the button "Upload to App Store", my best guess is that the AMChart library can be used for MAC and iOS apps, and for some reason the xCode organizer is not identifying it as iOS app...
I know i am missing something, but i am not finding it.
Thanks
Problem solved, i should change the skip install for the subproject under Build Settings.
SETUP:
OS X 10.9 13A603
Xcode 5.0.1 (5A2053)
I have a Mac app which is currently in the Mac App Store. This app is not distributed directly outside of the MAS.
I am trying to submit a new version for the first time in a while. This is the first time I've submitted with Xcode 5 (or Mavericks of course). In Xcode 5, there have been many changes related to provisioning profiles, code signing, and "Mac App Team" management (e.g. lots of "helpful" new UI).
I have also had to recreate my certificates and my development and production provisioning profiles for this app in particular. So a lot has changed since the last time I submitted this app to the MAS.
Note: my App target's Archive action uses the Release build configuration. So I use Release for submitting to the MAS.
PROBLEM:
I can't seem to simultaneously select the Signing: Mac App Store radio button in my target's General Tab while also selecting my distribution code-signing identity (3rd Party Mac Developer Application) in my target's Build Settings tab.
STEPS:
Assume my certificates and provisioning profiles are correctly installed (yes, I realize this is a big assumption, but everything seems to be installed and working properly. Let's just assume for a minute).
Open Xcode. Select my app's target. See General tab.
Select Signing: Mac App Store radio button. See Team popup change to correct team setting automatically. So far so good.
Click Build Settings tab.
Notice that Code Signing Identity is set to Mac Developer for both Debug and Release (Xcode changes this automatically whenever you select the radio button in the previous step)
Under Code Signing Identity > Release, change to 3rd Party Mac Developer Application (Apple's docs say this is the correct identity for MAS submission)
Go back to General tab.
EXPECTED:
Signing: Mac App Store radio button should still be selected
ACTUAL:
Signing: None radio button is now selected. Team popup has been changed to None.
NOTES:
Am I doing something wrong?
Does this even matter? If this radio button has no effect, I'm fine just ignoring it. But then why is it there?
Set the Signing radio box to None and configure your identity and provisioning in the target's build settings. I've never used that signing option in the general tab.
I'm pretty sure that the radio button is associated with the "automatic" code signing settings. If you manually specify a code signing identity the radio button will be set to "none", but your application will still be signed with the manually set identity and that is all that matters. (all this is assuming the certificate was set up for MAS distribution etc).
I have been archiving for ad hoc distribution fine for many months and suddenly today I cannot do so as the Archive menu item is disabled. I have not changed anything. I went through the provisioning setup for the project and it looks ok.
My Ad Hoc profile is about to expire in 14 days. Could this be the problem? I don't believe I can renew it until the day it expires. There is a a "renew" button for my ad hoc profile in the organizer but when I click it I get...
The given profile was not found on the provisioning portal.
Please refresh your provisioning profiles before attempting to renew “MyAddHocProfile”
The profile in the provisioning portal shows active, expiring on the 30th. I noticed that I had not yet upgraded to 4.6.2 and did so. Then I downloaded my profile and double cliked it thinking that would refresh the profile in Xcode, still no joy. I also tried manually replacing the profile file MyAddHocProfile.mobileprovision in the Library.
What do they mean "refresh your provisioning profile"?
Even so, I would think that as long as the profile is active, I should be able to create an archive. I must be doing something else wrong.
You've changed your scheme destination to a simulator instead of Generic iOS Device.
That's why it is greyed out.
Select "Any iOS Device" in newer versions of Xcode. And Archive Option will be enabled!
Change the active scheme Device from Simulator to Generic iOS Device
Select active scheme to Generic iOs Device.
In addition to the generic device (or "Any iOS Device" in newer versions of Xcode) mentioned in the other answers, it is possible that the "Archive" action is not selected for the current target in the scheme.
To view and edit at the current scheme, select Product > Schemes > Edit Scheme... (Cmd+<), then make sure that the "Archive" action is checked in the line corresponding to the desired target.
In the image below, Archive is not checked and the Archive action is greyed out in the Product menu. Checking the indicated checkbox fixed the issue for me.
If you are sure that you selected the Generic iOS device and still can't see the option, then you simply have to restart Xcode.
This was the missing solution for me as a cordova developer with Xcode 11.2
Organiser was empty after try every here recommended settings, also it was impossible to do 'Product > Archive' but... Only when device connected on cable and app run then 'Archive' show up. and then was possible to do 'Archive' and app shows up in Organiser
I am having a heck of a time trying to get this to work. At this point, I am only trying to create little test apps in xcode and "build and run" them on xcode-not on my phone.
I have a provisioning profile for my phone in the xcode organizer, but that is the only one I have.
Do I also need a separate provisioning profile for the desktop sdk?
You don't need provisioning profiles for developing on iphone simulator.
If you also want to develop on your device, first register the device when creating the provisioning profile, then upload the provisioning profile to your device.
Apple's documentation is pretty clear and easy to follow on this issue.
Good luck.
Edit: 1- You need provisioning for developing on the device, thats why it gives you a provisioning error when you try running with -iphone device xxx.
2-The blank white screen on the simulator has nothing to do with provisioning, you succeded to run your code on the simulator, but either your code does nothing or you did not link your uiwindow to your views
3-Base sdk defines that dropdown menu on the topleft. If you select iphone 3.1.2 as base sdk in project settings, you can only see simulator/device 3.1.2 on the dropdown menu, if you select 2.0 as your base sdk you will see device/simulator 2.0,2.1,2.2.1,3.0,3.1.2,... on the dropdown menu. Since you selected 3.1.2 as base sdk you don't see earlier versions on the dropdown menu.
You don't need provisioning profiles to run an app in the simulator, if that's what you mean. Just make sure you're Build-and-Go-ing for a simulator - iPhone Simulator 3.0, say - and you should be good to go.