Posts

Post not yet marked as solved
2 Replies
0 Views
It is a question. Moving from xcode 11 to 12.0.1 now causes a bunch of warnings. Asking if anyone has any ideas how to fix the warnings related to ... no longer supported; and warning: ignoring invalid debug...
Post marked as solved
8 Replies
0 Views
Solved by adding arm64 to Excluded Architectures (EXCLUDED_ARCHS) in the Project settings. Looks like we need to do this until the pod in question supports arm64.
Post not yet marked as solved
1 Replies
0 Views
Would check out the WWDC video at 7:30 for a companion app that can optionally run independently.https://developer.apple.com/videos/play/wwdc2019/208/Basically, in the watchkit extension target, just select 'Supports Running Without iOS App Installation'. This should set the info.plist parameters properly.If your watch app might need to communicate with the iPhone also (even though you also want it to run independently), then you should create the watch app by starting with 'iOS App With Watch App' template.If your watch app will not need to communicate with the iPhone at all, then use the 'App' template for a truly independent watch app.
Post not yet marked as solved
5 Replies
0 Views
I removed CFBundleDocumentTypes in my apps Info.plist (even though the array was empty). My app doesn't support any document types. Removing that key removed the warning for me when I re-build and re-submitted to iTunes Connect.
Post not yet marked as solved
2 Replies
0 Views
Hi, see this thread. Worked for me.May be a Xip issue.Solution proposed : Right-click on the downloaded .xip file and pick Open With > Archive UtilityLook at this : h ttps://forums.developer.apple.com/thread/80540
Post not yet marked as solved
3 Replies
0 Views
try a different app to unzip.
Post not yet marked as solved
3 Replies
0 Views
I'm also getting this with xcode 9 beta 4 after migration. When it goes away and I 'run', then get a 'property *** not found on object of type yyy. Where *** would be the item i am trying to pass to the swift view controller yyy. No error in 8.3.3 though.
Post not yet marked as solved
7 Replies
0 Views
In my case, using another program to open the xip file worked. Instead of 'The Unarchiver (default)' I used 'Archive Utility'.