app-store

I just bought a new iPhone XR so I could make the screenshots for my App Store app. Starting March 27th 2019, you need to provide 6.5" (new phone models) screenshots: However, App Store Connect is not accepting my screenshots made with this device. After further research, I found out that iPhone XR is actually 6.1": I am not from the iOS world (I mainly work with Google and Android), so I am wondering if I am missing something, or are the docs wrong? The iPhone XR and iPhone XS Max are the same size: 414x896. The reason your screen shot is coming out the wrong size is that the iPhone XR is

So I've tested my application's In App Purchase content at length during development using the Sandbox mode. For some reason now that the application is live in the App Store when clicking the purchase button nothing happens at all. It looks like the Apple review team was able to successfully complete a purchase based on server logs (could be wrong about this tho). I'm using SwiftyStoreKit to handle in app purchases. Any ideas why it would work perfectly during development and in sandbox mode and not even do anything when calling the SwiftyStoreKit.purchaseProduct method in production? If I

With Apple's new requirement to have a 64 bit build support, apps executable are getting bigger. After several attempt to reduce the final build size to something < 100mb I was wondering if it was possible to drop 32 bit support and only support 64bit. Building an app for 64bit only works fine but the submission process seems to prevent such behavior. Adding this non-documented UIRequiredDeviceCapabilities does not change anything as the error becomes the following I checked that there is no mention of armv7 or armv7s in my architectures settings Yet people on the Unity forum seems to say that

I have an app on app store, which is using an iOS Provisioning Profile (Distribution) which is invalid. This Profile contains Push Certificate. so I want a regenerate Provisinig Profiles. Q. when I update Appstore app with renew Provising Profile, pushservice of current Appstore app version is working fine? (I just renew Provising Profile and same Certificate, same AppID) Thanks for your help on this :) As you mentioned in your question that Provisioning profile is Invalid. So i guess certificate is expired & you are going to renew it. If so than yes current app store version will work fine.

I have an app in enterprise appstore and the provisioning profile with which I created iPa is due to expire next month. If I go to developer account and renew the provisioning profile, what happens to the app in appstore which was created with old provisioning profile? Should I create a new iPa with new renewed provisioning profile and submit it? Is it enough to just renew the expiring provisioning profile or should we renew, create iPa with new one and upload it to appstore again? Any help would be appreciated. Thanks! You will need to provide a new provisioning profile, that has a new

On a iPhone 4/iOS 4 device, sandbox App Store is reporting this error during verification. 21002: The data in the receipt-data property was malformed. On a iPhone 5/iOS 6 device, the same code works (status == 0, receipt returned) without any problems. I've restarted the device, made sure the Apple ID is logged out, even made a new test user account. Same result. Any ideas? This Error means the JSON Object that you have created to send for verification is not in correct format. { "receipt-data" : "(receipt bytes here)" } So My suggestion is to Debug the same on iPhone 4/iOS 4. In case, you are

I'm just preparing my app for iOS 9, prior to the new release next week, using latest beta version of Xcode but it gives me this error message: Nope, you cannot with beta versions of Xcode (same as with previous beta versions of Xcode). Now the newest Xcode version is the 7.1 beta which cannot be used for publishing apps. But there is Xcode 7.0 GM version and with this one it should be possible to publish app. Now when I am uploading apps it gives me same warning ( "Invalid Toolchain..." ; but I have it in testing for internal testers, I am uploading app via Application Loader ) but it shouldn