Post not yet marked as solved
Previously on 11.2.3 I was able to run my OpenGL game targeting my M1 Mac mini as an iPad game. After updating to macOS 11.3 I am now getting an error in Metal. Is this expected moving forward and a sign that we need to focus on porting to Metal sooner rather than later?
-[_MTLFunctionInternal baseObject]: unrecognized selector sent to instance 0x13046dab0
Crashing on:
glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_SHORT, nullptr);
Thanks,
Steven Behnke
Post not yet marked as solved
We have some developers on our team experiencing a crash while trying to debug.
Message from debugger: The LLDB RPC server has crashed. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log. Fatal error: Invalid position SourceEditorPosition: line: 244, col: 38 with line length 26 : file /Library/Caches/com.apple.xbs/Sources/SourceEditor/SourceEditor-17136/SourceEditor/SourceEditor/CoreEditor/Model/SourceEditorDataSource.swift, line 2710
This is happening with breakpoints in specific spots in our mostly C++ codebase. It is happening in Xcode 12.0.1 and did not happen in the same version of Xcode in our branch without the Widget Extension added. Is there anything we can do? We've reported it with Apple Feedback and heard nothing back. We're going to try to reproduce it on Xcode 12.1.1 RC.
I am attempting to format a timer with the code:
Text(Date().addingTimeInterval(2400), style: .timer)
It does indeed work fine for the content, but the text field appears much longer than it should. I want to center this text under another text entry so I used a VStack, but the timer appears left justified and does not align on center based on the content.
If I write my own method to provide just the limited characters I want, I can indeed center it without issue, but this does not countdown once per second for the widget view. I suppose I could get around this by adding 3600 timeline entries for the next hour, but I don't think that would be a great solution.
Is there any way to resolve this? I can kind of get around it by adding a frame that fits for the case of 00:00 or 0:00 but not both.
