Posts

Post not yet marked as solved
68 Replies
55k Views
Hello!I would like to initiate an App transfer for one of my Apps. When I click the "Transfer App" button I get a message telling me that one criteria is not met: “You must turn off TestFlight beta testing for the app that you want to transfer”. I turned off Testflight by checking the checkbox "Not Available for Testing" for Internal and External testers. Unfortunately I still get the same critertia not met message.After a google search I found out that I might have encountered this bug:http://stackoverflow.com/questions/32906771/itunesconnect-cannot-transfer-app-because-of-you-must-turn-off-testflight-beta/32909981#32909981Does anybody have a solution for this? Since the discussion was started already on Oct 2nd and there is still no real workaround/answer for it I am not sure if I didn't miss something else when turning off Testflight.Is there anything else to do besides setting Internal and External testing to "Not Available for Testing" or is this indeed a bug in iTunes Connect which hasn't been fixed for over 2 months now?Thanks!
Posted
by domhof.
Last updated
.
Post not yet marked as solved
7 Replies
2.9k Views
I was able to reproduce this with our own app as well as with apps by other developers (e.g. Documents by Readdle).Our app stores its data in the app group:Foundation.FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: AppGroupConstants.appGroupIdentifier).appendingPathComponent("File Provider Storage", isDirectory: true)!.appendingPathComponent("Media", isDirectory: true)1) Install the app from the App Store2) Add some data3) Manually offload the app (Settings -> General -> iPhone/iPad Storage -> *App Name* -> Offload App)4) Backup device to iCloud5) Reset device (Settings -> General -> Erase All Content and Settings)6) Restore device from iCloud Backup (this is important - it works with iTunes backups)7) Open the app. Because it was offloaded it gets downloaded at this point but the app group data is NOT restored.This looks like a serious bug to me.Can someone confirm this?
Posted
by domhof.
Last updated
.
Post not yet marked as solved
0 Replies
1.4k Views
Our FileProvider-Extension used to work perfectly in previous iOS versions. Starting with iOS 13 we keep getting the following error randomly when accessing files (stored in the app group):Error Domain=NSCocoaErrorDomain Code=4101 "Couldn’t communicate with a helper application." UserInfo={NSUnderlyingError=0x281edd1a0 {Error Domain=NSFileProviderInternalErrorDomain Code=7 "A connection to the extension “com.ourdomain.ourapp.DocumentProviderFileProvider” could not be made." UserInfo={NSLocalizedDescription=A connection to the extension “com.ourdomain.ourapp.DocumentProviderFileProvider” could not be made., NSUnderlyingError=0x281edcb10 {Error Domain=NSCocoaErrorDomain Code=4097 "connection to service on pid 0 named com.ourdomain.ourapp.DocumentProviderFileProvider.apple-extension-service" UserInfo={NSDebugDescription=connection to service on pid 0 named com.ourdomain.ourapp.DocumentProviderFileProvider.apple-extension-service}}}}}Our FileProvider implements these methods:func itemChanged(at url: URL)func providePlaceholder(at url: URL, completionHandler: ((_ error: Error?) -> Void)?)func startProvidingItem(at url: URL, completionHandler: @escaping (Error?) -> Void)func stopProvidingItem(at url: URL)The error happens rarely (only in ~1 of 100 tries). When it does, first the UI freezes (the device doesn't react to touches) for about 1 minute and then the error gets thrown by iOS. Sometimes if you retry to acces the file, the error goes away (file can be accessed), sometimes the error persists. This looks like a serious iOS-bug to me (at least in previous iOS versions the FileProvider, as mentioned, worked perfectly - and no changes have been made to the code).Has anybody experienced similar issues in iOS 13 with a FileProvider-Extension?
Posted
by domhof.
Last updated
.