Post not yet marked as solved
We found the issue. We had inadvertently added a folder called "Configurations" to the target with a json file in it and for some reason Xcode was adding this to the MyApp.app/Frameworks directory in the DerivedData folder as part of the build process.
The trick to discovering this was working out where MyApp.app/Frameworks is and looking at what is in it. Look in the Derived Data folder (XCode/Settings/Locations/Derived Data
for us:- The derived data folder is /Users/myname/Library/Developer/Xcode/DerivedData/
and looking in there under MyApp name .......
/Users/myname/Library/Developer/Xcode/DerivedData/MyApp-afmktkuorsjstcffmzapfvdxtlqs/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/BuildProductsPath/Release-iphoneos/MyApp.app/Frameworks/Configurations
So we removed Configurations and its contents from the target ( the json was not being used) and AppStore Upload is happy again.
Post not yet marked as solved
I have found a solution , see this post [https://developer.apple.com/forums/thread/742594]
Select the relevant product in the the Scheme dropdown (e.g. "[AppName] Watchkit App", or "[AppName]" for iOS app
Select "Edit Scheme..."
Select "Run" in list on the left
Select "Arguments" tab
Click ">" next to "Environment Variables" to show a (probably empty) list.
Click "+"
In "Name" column, double click the space and enter: IDELogRedirectionPolicy
In "Value" column double click the space and enter: oslogToStdio
Ensure the checkbox is selected
Click Close button.
You have to repeat these steps for each iOS, WatchOS product as each has its own Run Scheme.
Now NSLogs will print to the Debug Console again.
Post not yet marked as solved
Same here with trying to run Xcode debug on real device. XCode 15.0.1 , watchOS 10.1.1
Post not yet marked as solved
Solved. The magnets in the iPad Magic Keyboard were the problem, they were messing the magnetometer up. Once the iPad was removed from the case all works fine.
Post not yet marked as solved
Has anyone found a solution to this? Has Apple provided a way of giving a watchkit pin annotation a name?
Post not yet marked as solved
We are having this problem again on iOS15 running over Bluetooth. Session connects successfully over Wifi but never gets to connected over Bluetooth. Over bluetooth it gets to connecting state receiving the invite in didReceiveInvitationFromPeer which we handle but then never gets any further and eventually timesout. We are using the apple sample Streaming an AR Experience app ( https://developer.apple.com/documentation/arkit/streaming_an_ar_experience )
Is anyone else able to get this working over Bluetooth on iOS15?
Post not yet marked as solved
Apple, are you listening!!!!!!!!!!
please address this, it's extremely frustrating. Just how many times does it need to make my iPhone ready for development?
Post not yet marked as solved
we have the same issue. Any suggestions?
