Still a bug in iOS 14.4 Beta 2 - 1/13/2021 - 4 months and (painfully) counting....
Post
Replies
Boosts
Views
Activity
Still a bug in iOS 14.4 Beta 2 - 1/13/2021 - I was hopeful 2021 would bring a fix.
And if anyone who has any influence on getting this fixed needs a little nudge, please notice that this bug is over 4 months old.
Still a bug in iOS 14.4 first beta (12/16/2020)
I just installed iOS 14.3 RC and this bug is still there. Very frustrating that this bug has been in the public iOS and known to Apple for more than 3 months!
I just installed iOS 14.3 RC and this bug is still there. Very frustrating! If anyone knows anything about the status of this bug could chime in, it would be great. An outstanding bug for more than 3 months is troubling.
“Apple Silicon”
Just installed iOS 14.3 beta 3 and this bug is still there. Is there anyone watching this thread that can offer any help or additional information?
@RobertManea Yes, I see those lines in the console for the device, but never get anything in the Xcode console after it hangs.
Thanks for chiming in to let me know I'm not the only one.
BTW - there is another post from a few years ago when a similar (or the same?) bug was present - that post said you could create a playlist, wait a few seconds, then addItemWithProductID would work. But my testing this time around shows that the solution doesn't work ;-(
I've submitted this via feedback assistant (FB8820341) and used a trouble ticket from my dev account (FYI - they charge you for the incident even if it's a bug and there is no resolution) and it's still an issue in the first iOS 14.3.
I've received no info from Apple on when/if/how this can be fixed.
Hate to be the bearer of bad news but if you're having the same issue, at least you know you're not alone.
Thanks for your help, Eskimo! I feel less defeated knowing that you had the same trouble ;-)
I'll try a DTS support ticket and update here if any solution is found in case it can help someone else.
I'm having this exact issue with Xcode 12.1 - I didn't have it previously and was actively submitting watchOS apps during the times of this original thread.
I've checked my valid architectures and all are set to Standard.
Did anyone find any other causes or ways to get around this?
Seems to still be a problem in iOS 14.1 as I outlined in this post:
https://developer.apple.com/forums/thread/664336
Has anyone filed a bug report?
Deployment for iOS app: iOS 12.0
Deployment for watchOS: 5.0
I updated to Xcode 12.1 & tried updating deployment to iOS 13.6 & watchOS 6.2 but still get the same error.
Thanks for your continued help. Any other ideas?
Thanks again, Eskimo, for your quick help. I did as you recommended and found the code signing identifier and bundle ID matched as expected for the app. In the /watchkitsupport2 folder there is one file named "WK" - I think that's the nested watchOS file you mention. When I run codesign for WK file:
Executable=/Users/davenorfleet/Downloads/MyFitnessDJ 2020-10-20 08-19-11/MyFitnessDJ/WatchKitSupport2/WK
Identifier=com.apple.WK
Format=Mach-O universal (armv7k arm6432)
CodeDirectory v=20400 size=453 flags=0x0(none) hashes=9+2 location=embedded
Signature size=4628
Info.plist=not bound
TeamIdentifier=not set
Sealed Resources=none
Internal requirements count=1 size=60
So it seems the Identifier, com.apple.WK, is being set here from something.
Also, although I use automatic signing for iOS app & watchOS app & watchOS extension, I get a prompt while distributing in Organizer saying that "appname_ needs to be re-signed for App Store Connect distribution." I select automatically manage to continue.
Does that give you any more clues as to what the problem may be?
Sorry to miss those details, it's an iOS app with embedded watchOS extension. Building with Xcode 12.0.1 then submitting using Organizer.