Posts

Post not yet marked as solved
7 Replies
2.1k Views
Something has broken when doing a non-consumable in-app purchase in iOS16 when compiling with Xcode 14.0.1. The exact same code worked fine in previous versions, but I cannot determine the cause of this new strangeness. The symptom is that the purchase of our app cannot be restored in any way. This problem seems to be only with the actual App Store. Restoring purchases works perfectly on iOS 15.7 and 16.0.2 when testing either in a sandbox environment or the new Xcode environment, but when dealing with the actual App Store, no dice. The result with the App Store is that there is no response whatsoever after initiating SKPaymentQueue.default().restoreCompletedTransactions(). The transaction.transactionState function never returns anything at all, not even a .failed. If I try and re-purchase the app, then transaction.transactionState immediately returns a .purchasing value, but then nothing completes from there. So there appears to be no way to restore or repurchase it for free even. Here is more detail using the same code that has worked fine for quite some time, up until now:  - the version we have on the App Store currently restores fine on both iOS 15.7 or 16.0.2 (unsure what Xcode version I used to archive and distribute this version initially…could be Xcode 13.*)  - testing in the sandbox or Xcode test environment, the app restores fine on iOS 15.7 AND on iOS 16.0.2  - uploading and using TestFlight, the app restores fine on iOS 15.7, but does NOT restore on iOS 16.0.1 or 16.0.2 This was also happening on Xcode 14 before I updated to 14.0.1. Things I’ve tried to help narrow it down, but to no avail:  - Removing and reinstalling Xcode 14.0.1  - Regenerating the certs and provisioning profiles on my MacBook  - Multiple iOS configs across four devices to try and find a logical pattern (details above…) I could use some guidance on this, as it seems that releasing a new version will likely not function on iOS16.0.X when using Xcode 14.0.1 until I solve this. I’m dead in the water.
Posted
by Adalex3.
Last updated
.
Post not yet marked as solved
1 Replies
977 Views
I want to be able to pull up a certain song in the user's iCloud Music Library in the Music app from my app. I know it's possible to use one of Apple's APIs to pull up a song based on a search query in the iTunes Store, but I'm wondering if it's possible to go directly to the Music app is the user has already purchased that song. If I have the song as an MPMediaItem, maybe I can input a search query with the data from that MPMediaItem and go from there.The key might be in the Apple Music API:developer.apple[dot]com/documentation/applemusicapiI don't know enough about it or anything else that might of use to this situation.How can I go about doing this?
Posted
by Adalex3.
Last updated
.
Post marked as solved
25 Replies
48k Views
I am simply trying to run my app on my iPad through lightning cable but I am getting this strange error:Could not launch "[App Name]"[Device name] denied the launch requestI have looked all over the internet for an answer to this but cant seem to find a good solid fix.I have tried everything from deleting the app on my iPad to cleaning the project to restarting many times but nothing will work. Right now I am running Xcode 9 beta so I tried switching to Xcode 8.3.3 and testing it there. I get a different error:Could not launch "[App Name]"process launch failed: UnspecifiedNext, I tried doing it on the simulator to see if it was any different. The outcome was a continuous loop of the app opening and crash, then opening again, and crashing again. After about five minutes of this loop, I got this error:The request to open "com.hp.Goal-Tapper" failed.The request was denied by service delegate (SBMainWorkspace) for reason: Unspecified.Does anyone know how to fix this? I am a beginner at Xcode and swift so I won't know very complicated things. Thanks in advance. Any help is appreciated.
Posted
by Adalex3.
Last updated
.
Post not yet marked as solved
2 Replies
1.2k Views
My app requires that location updates happen in the background for it to function. The app worked fine in iOS 12 as I had the Background Mode "Location Updates" turned on, but in iOS 13, the app only runs for about 30 seconds or so before stopping background function. How can I fix it so that my app can still get location updates in the background in iOS 13, while preferably still holding out support for iOS 12?I found this article (medium(dot)com/swlh/handling-background-tasks-in-ios-13-67f717d94b3d) that talks about iOS 13 limiting app background functionality to about 30 seconds, which I just can't believe is true. There are so many apps that require background processing to happen all the time like mine.
Posted
by Adalex3.
Last updated
.
Post marked as solved
1 Replies
2.4k Views
I have an existing app that uses Core Data to store many things, and I would like to make it so that the Core Data data will be uploaded to iCloud and will be able to be synced between devices with the same app. I've looked into this a little bit but havent found a case the same as mine. I've found this stackoverflow[dot]com/questions/27669173/swift-replace-core-data-with-icloud-core-data stackOverflow psot about something similar but not the same.For reference I have a storage model with three entities with tons of attributes (but nothing else) that I want to be synced.How can I do this?
Posted
by Adalex3.
Last updated
.