On Xcode 4.6.3 this delegate method below works good:
- (void)productsRequest:(SKProductsRequest*)aRequest didReceiveResponse:(SKProductsResponse*)response;
But when I try to run the same project on Xcode 5 it does not work. Instead of invoke delegate method above the app calls this method:
- (void)request:(SKRequest *)request didFailWithError:(NSError *)error;
I have description of error:
{NSLocalizedDescription=Cannot connect to iTunes Store}
I use standard iOS 7 simulator and Xcode 5 but in this case the logic does not work as I expect.
For version 4.6.3 all work
My comment is actually the answer, further digging shows Apple doc for Xcode 5 release notes says under the iOS Simulator section
StoreKit (In-App purchases) will not work in the Simulator
Here
As I said in another post, even if it's not the desidered behavior of the question, you can still test IAP from Simulator & Xcode5 if you deploy and run/test for iOS6 (with test user, sandbox environment, etc...).
For me, this solution is better than deploy on device in early staging of developing phase.
Mick.
Related
but I have an iPhone 13 plugged into my MacBook Pro. I know this might seem like a strange question, but when I try to build & run my app the following messages notify me
This iPhone 4 is running iOS 15.6.1 (19G82), which may
not be supported by this version of Xcode. An updated
version of Xcode may be found on the App Store or at
developer.apple.com.
I cannot remember when the following notification came to my attention, but it basically displays the same message and I took a screenshot of it when it occurred
I have contacted Apple, but I am on my second tech, who is asking me about my browser version, etc... which tells me that they are stalling - no browser, an app build & run in Xcode. An app literally targeting iOS 11.0 and above
When I run my watch kit app (WatchOS 2) in Xcode 7, Swift, it installs and then finishes (stops). No error messages, it just stops. I've uninstalled and re-install both the IOS app and the watch app. No luck. Runs fine in the simulator. If I create a new empty project, same behavior. When I check the watch app on the watch, the new build is installed. It just doesn't run from Xcode so I can't get my debug messages. I am using the scheme for the IOS app and the Watch App. Is there anything to look for in the scheme config? I have also recently updated my provisioning profile and development certificates.
I've tried looking at similar questions, but so far they have not helped.
Xcode successfully builds my target, but does not run the product
Debug/Run in Xcode stopped working. Executable settings are wrong and can't be fixed too
and similar to:
"This app contains an app extension with an illegal bundle identifier" issue
There's several people with this problem. I can't give you any tips for iOS 9.0 and XCode 7.1 (Besides, reseting everything and trying again). But, If you update to watchOS 2.1, iOS 9.2 and XCode 7.2, everything works.
With device connected, shut downing my iPhone and watch and then restarting fixes the problem.
I have a blank app, which is having none code.
I've generated corresponding provisioning profiles for it and attached them to it.
I've set the compiler options - generate universal binary.
I have Mac OS X 10.11.1 ( El Capitan ), XCode 7.1, iOS SDK 9.1, Delphi 10 Seattle.
I am testing on iPad 3 / iOS 9.1 and iPhone 4 / iOS 7.1.2
When I try in debug and adhock - the app runs like charm, anyway my builds is rejected in Apple Application Store by the reason :
"2.1 Details
We were unable to review your app, as it crashed on launch.
Next Steps
Please revise your app and test it on a device to ensure it will launch without crashing."
What could be the possible reason of causing this issue ?
It turns out that the hint #BinaryGuy have made is solution of the problem.
Seems like UI_USER_INTERFACE_IDIOM is kept and linked into the compiled IPA if the developer use some of the classes containing a link toward it.
The classes which causing the issues is primarely related to the previously accessible hardware ID's on the Apple products, now these classes seems like is deprecated and causing the Application Store rejection without obvious reason.
Please if You are using some of the follow Delphi units :
FMX.Helpers.iOS.pas (TUIDevice / UIUserInterfaceIdiomPad references),
iOSapi.UIKit.pas (UIUserInterfaceIdiomPhone references),
FMX.Platform.iOS.pas (UIUserInterfaceIdiomPad references),
double check if they could be avoided.
The Watch App is installed on the watch and I can tap and run it on the Watch, but watchAppInstalled method returns false.
Also, I can only install the Watch App using Xcode 7. If I try to install the Watch App using the Watch iOS app (from Apple) by turning on the switch, the Watch App gets deleted right after the installation completes.
Update:
This bug is fixed in Xcode 7 beta 6
Apple Documentation says:
The session must be configured and activated before accessing this
property.
So, you should configure and activate the session before using this property.
I had same issue.
I just add WatchConnectivity.framework to my main app target and watch extension target. And it works now.
Hope i helped.
Cheers.
Update: i read comments above and check my architecture: already had arm64
What worked for me was adding the arm64 architecture to both the Watch app and iOS app as #Zubair suggested.
Update:
This bug is fixed in Xcode 7, beta 6
It now works for me, what I did:
Reset and Re-coupled the Apple Watch and added a Passcode to it (what I never did before).
Edit: You can then safely disable the Passcode and it will still work.
I can't upload an app to iTunes Connect.
Xcode uploader says that I'm using allocBatch:withEntity:count:, allocWithEntity:, IndexForKey:, fastIndexForKnownKey:
I'm not using this methods, and I don't know where they could be. A week ago same code was uploading successfully. What can be the cause of such behavior?
UPDATE
Submitting with older Xcode is not working anymore, this error reveals on binary processing.
I had this exact issue using Yosemite with Xcode 6.1 and using Objective C. I also got a warning on validation saying you can't upload an app created with a beta version of Xcode, which 6.1 is at the time of writing this.
I trashed Xcode 6.1 by dragging it to the trash form Finder then downloaded Xcode 6.0.1 GM from the App Store. I tried twice to install 6.0.1 over the top of 6.1 but it didn't work, hence the trashing of 6.1
Having cleaned and recompiled my app with Xcode 6.0.1 it validated and submitted to the app store with no problem. I hope this helps.
I fixed it by changing the deployment target from iOS4.3 to iOS5.0 all fixed using Xcode 6.1
I encountered the exact same error when using Xcode 6.1 (and its bundled Application Loader) on Mac OS 10.9.5. Clicking "Back" within the Application Loader and re-submitting the same binary worked. In other words, trying a second time succeeded. My app was built with iOS SDK 8.1.
You don't have to delete XCode 6.1. It would become handy in couple days. Just download XCode 6.0.1, copy it somewhere, and use sudo xcode-select --switch /Applications/Xcode601.app/Contents/Developer/. Then start it, and build your great app with it.
The API differs between iOS 7 and iOS 8. I got my App validated by switching to Deployment Target "8.0" - built with XCode 6.1. It might not be the solution to all you guys but you could give it a try.
Might have happened to me because I recently started using UIAlertController -> seems to be an iOS-8-Feature. On iOS 7 this would be UIAlertView. So if you use some nifty new features they might not have been available with previous iOS versions - thus non-public API.
Increasing the version number of my app did the trick for me.
EDIT: Just saw a comment in my bug report to apple
So most likely the version number had nothing to do :D
I got the same problem in Xcode 6.0.1 if I use the archive created by Xcode 6.1. It works if I recreate the archive by Xcode 6.0.1. That means the non-public API is added by Apple in Xcode 6.1.
I tried to delete all DerivedData.
/Users/{user_home_folder}/Library/Developer/Xcode/DerivedData
and I validated successfully.
http://qiita.com/PGMY/items/831618ad416780e0dc7c
i had meet same issue when i cancelled archiving to app store. Apple send me email about this subject. And than i recreate archiving and send to App Store. Everythink is ok for a now.