Can't run/debug on iOS 14 using Xcode 12.0 or 12.2 using Big Sur Beta 7?

Question

Created Sep ’20

Replies 9

Boosts 0

Views 4.5k

Participants 6

Not sure when this started to happen, but I can't run/debug my app from Xcode using the latest beta of Big Sur.

I'm trying to deploy to the iOS 14 GM on my iPad using Xcode 12.2 (12.0 also doesn't work) from Big Sur beta 7 and it shows up as a blank screen and then eventually crashes, without an error in Xcode.

Anyone else experience these kinds of issues or might have an idea of what's going on?

Here's the crash report from the console though:

Code Block Incident Identifier: B8250B7F-0F22-4803-92E2-81AB9395F31ECrashReporter Key:   810e5f7e3b9c5c05f37139678fb17d5c6262be0d
Hardware Model:      iPad8,7
Process:             RocketTest [1120]
Path:                /private/var/containers/Bundle/Application/CEA74FA4-9710-4070-B0F9-826A7C00FA14/RocketTest.app/RocketTest
Identifier:          com.igottabelieve.RocketTest
Version:             1 (1.0)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      Exited process [1117]
Coalition:           com.igottabelieve.RocketTest [422]
Date/Time:           2020-09-19 21:14:22.2745 -0500
Launch Time:         2020-09-19 21:13:59.4436 -0500
OS Version:          iPhone OS 14.0 (18A373)
Release Type:        User
Baseband Version:    3.00.01
Report Version:      104
Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000001012d08b8
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [1120]
Triggered by Thread:  0
Thread 0 Crashed:
0   dyld                          	0x00000001012d08b8 0x1012c0000 + 67768
1   dyld                          	0x00000001012cfd6c 0x1012c0000 + 64876
2   dyld                          	0x00000001012cfa10 0x1012c0000 + 64016
3   dyld                          	0x00000001012c59c0 0x1012c0000 + 22976
4   dyld                          	0x00000001012d1e60 0x1012c0000 + 73312
5   dyld                          	0x00000001012c5f8c 0x1012c0000 + 24460
6   dyld                          	0x00000001012c7afc 0x1012c0000 + 31484
7   dyld                          	0x00000001012c1258 0x1012c0000 + 4696
8   dyld                          	0x00000001012c1038 0x1012c0000 + 4152
Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x00000000000001be   x2: 0x000000016eef25c0   x3: 0x0000000000000000
    x4: 0x0000000000000000   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000000000000
    x8: 0x0000000000000000   x9: 0x000000016eef33b0  x10: 0x00000001a65fd000  x11: 0x0000000101354970
   x12: 0x0000000101339360  x13: 0x00000001ef739b5a  x14: 0x000000000000000d  x15: 0x000000008000001f
   x16: 0x00000001012cb914  x17: 0x0000000000000010  x18: 0x0000000000000000  x19: 0x0000000000000000
   x20: 0x000000016eef6c80  x21: 0x00000000000001be  x22: 0x0000000101338000  x23: 0x00000000000001be
   x24: 0x0000000101338620  x25: 0x000000016eef26a0  x26: 0x0000000000000014  x27: 0x000000001f070018
   x28: 0x000000016eef18b0   fp: 0x000000016eef3450   lr: 0x00000001012cfd6c
    sp: 0x000000016eef25c0   pc: 0x00000001012d08b8 cpsr: 0x80000000
   esr: 0xf2000000  Address size fault

Boost

Answer 1

postng OP

Sep ’20

Same same.
No log at all on Xcode 12.2. But, if I wait 3minutes on the blank screen it suddenly starts and runs normal.
Also no log or timeout info what happen on Xcode.

0

Answer 2

rrrruuubyyy OP

Sep ’20

Same here,
2015 MacBook Pro on Big Sur (20A5364e), Xcode Version 12.0 (12A7209), iPhone XR with iOS 14.0.

Running/Debugging works in Simulator but unfortunately not on Hardware. I get a blank screen. If the app is started without Run/Debug it works correctly.

As with postngs answer the app runs correctly after 2-3 minutes in Run/Debug.

0

Answer 3

sammyjojo OP

Sep ’20

Yes, that's exactly what I'm seeing. I didn't let it sit long enough to know that it would run after a while. It's nice to know that I'm not the only one experiencing this problem.

I can't figure out a solution though 😔 I'm tempted to install iOS 14.2 to see if that will work like it used to.

0

Answer 4

sammyjojo OP

Sep ’20

Just wanted to give an update to anyone still experience a similar problem.

Updating to iOS 14.0.1 (iPadOS for me) fixed the problem for me. I'm also on Big Sur Beta 8, but before updating to iOS 14.0.1 it wasn't working.

0

Answer 5

RobCohen OP

Sep ’20

I have the same issue, but I’ve not waited long enough for a crash. I’m running Xcode 12 (release) and iPadOS 14.0.1 and Catalina 15.7? Or something like that. Also can’t seem to debug the app - there’s no console or anything...makes it hard to be productive.

0

Answer 6

RobCohen OP

Oct ’20

I have a new clue to this problem....

The app is stuck at the LauchScreen.storyboard. But if I wait long enough (20-30 seconds), I see this message in the console:

Code Block Metal API Validation Enabled

And then it works. Far from ideal...

0

Answer 7

oviano OP

Oct ’20

I am getting this issue on macOS Catalina 10.15.7 + Xcode 12.0.1 trying to debug an application on an iPad Pro running iOS 14.0.1.

It launches to a black screen and then waits several minutes before starting and debugging. There is also a lengthy pause (about 8s) after it displays the first rendered frame before continuing to run properly.

The application launches normally if I subsequently launch it from the iPad without using Xcode.

0

Answer 8

oviano OP

Oct ’20

So this issue disappeared for me after I upgraded my iOS device to 14.1 and Xcode to 12.1. I don't know which of these steps solved it, maybe both are required.

I also unpaired and repaired my iOS device.

0

Answer 9

mustafa sait OP

Mar ’21

I still have the same problem in Xcode Version 12.4, ios simulator 14.4 and BigSur 11.12.1.
It only happens with ios 14+ simulators.
It shows black screen with an activity indicator then detach debugger and return to simulator's home screen.
Xcode shows me Message from debugger: Terminated due to signal 9 error.

0