Fix incorrect extraction of the get-task-allow flag from the provisioning profile #850
Conversation
|
Thank you, with 3725 I can build but I can not copy to device, it says no device found although I can see the device and I can install the app via Devices and Simulators in Xcode. There is one more thing happening with iOS, it seems we can not see print results in Console anymore on device, I thought it is because it is downloaded from store but even development builds the situation is the same. 
Sorry to bother you but it makes really hard to debug on device, like ads or ump. Thanks and Best Regards |
|
Yes @bulupe, there are still 2 issues in Tahoe one is the unreadable console and the other is that mono audios doesn't play, only stereo. Weird it doesn't install though, I do the whole build and install process through the command line so I haven't tested doing so from the simulator. |
3 participants
Fixes an invalid provisioning profile issue I have been facing since I upgraded to Tahoe.
https://forums.solar2d.com/t/ios-deploy-fails-after-macos-upgrade-a-valid-provisioning-profile-for-this-executable-was-not-found/357564
I get this log from the Engine when building with
debugBuildProcess = trueget_task_allow_setting: "get-task-allow" => trueWhen the expected is just:
get_task_allow_setting: trueI have been able to resign my app properly with that command, but I haven't been able to test this change from the engine itself.