Post not yet marked as solved
Experiencing this issue with Apple's own Support Forum from iPadOS 15 beta. Log in with fingerprint id, type a message, immediately get a session timeout asking me to "recover" my message, which asks me to log in again, but discards the message I typed. And attempting to type a new message and submit it results in the same session timeout.
Post not yet marked as solved
I got this error from Xcode when attempting to compile this rather simple floating point constant:
Float((1.0 / 255.0) * 0.5 - (1.0e-7 * (1.0 / 255.0) * 0.5))
It's a clipping constant for 8 bit per pixel image data in the floating point space.
Post not yet marked as solved
Just thought I'd add my own experience, since the other topic is now locked, and it seems relevant to this topic. I one again experienced this error 1048 submitting Developer ID bundles for notarization. It seems I needed to log into developer.apple.com, which somehow hadn't authorized this particular computer for login yet. Once I'd logged into it in Safari, and checked that everything was in order, I am now able to upload app bundles for notarization automatically.
This may require redoing any time your IP address changes, or, in the case of one user in this topic, if you are accessing via a VPN or proxy of some sort.
E: Note, that signing the contracts is not within my capability, since the signing team I am using, I am only a "user" level, so I just have the team's Developer ID certificate and access to the team profile and some of the settings. I still need to bug the team leader whenever the agreements have changed and need to be reviewed and re-signed, which does happen periodically, but isn't what was causing this error for me.
It is perhaps the right thing to do, as it seems the 11.0 version is on hold once again. The Xcode 12 GM doesn't even target Big Sur with a 10.16 or 11.0 SDK, and is no longer a Universal app. Perhaps this whole Nvidia buying ARM thing has made them reconsider the whole thing.
And now it's doing it again with Xcode 11.2.1.And it's also taking upwards of 5 minutes to get a 2FA code to appear on any of my devices.E: Okay, I found I could successfully notarize by using the manual altool method. It seems it was picking up the fact that my account's primary team, a personal team, is expired. I had to use altool with the correct team shortcode for the developer team I am a member of and have access to a Developer ID certificate for.
And now it's happening again with my own project file. I cannot notarize and release updates now. I do not think having to use the beta is an appropriate action, either, if that somehow fixes it.
This is happening to me now, after I have just updated to 10.15.1 stable, still using Xcode 11.1. Posted feedback FB7417718.
New answer for Developer beta 3: Now it always shows daytime background when dark mode is activated.
Post not yet marked as solved
Don't forget to take a sysdiagnose dump and forward it to Apple in a bug report. Apple doesn't really read this forum for troubleshooting or bug catching.
Apple has told Oracle exactly what they need to do to fix their kernel extensions. It's out of your control, unless you too have a kernel extension signing key, or want to run unsigned kernel extensions.
I find there are issues with both the camera and the audio input, with several applications. Initiating audio and video input causes most of the system to hang, until the requesting application is Force Quit. This is regardless of if permission has been granted for access.
Post not yet marked as solved
Discord is still broken in beta 2. It hangs when attempting to capture audio, and manages to hang most of the system in the process, until it is Force Quit.
Post not yet marked as solved
Further note on Discord.Even Canary has issues maintaining video calls for longer than 20-60 minutes, before the app will crash and report an error.It looks like I'll have to do Discord's job for them and report the bugs on the bug tracker, since they're not concerned with anything that isn't already a known major crash issue. They already have a crash issue on their hands with Canary that affects everything back as far as Sierra, and now there's a new issue that's only cosmetic, and therefore unimportant until Mojave is released final, when it'll be too late to report OS issues as OS issues.The other issue that Canary experiences, is that the icon is invisible when there's a badge. It's just an empty space with a number badge applied to it, showing that they use something unusual to composite their icon and badge together. Possibly an image resizing algorithm that's been removed, or is buggy?This level of instability with video calling apps renders Mojave unusable for me as a daily use test platform. So glad I stuffed it on an alternate APFS volume.
Post not yet marked as solved
You probably mean Xcode 10 beta. Xcode 9.4 is the current stable release, and still works on Mojave. Of course, if you're nuts enough to be using Homebrew or MacPorts on Mojave, you'll probably be forced to at least have Xcode 10 beta installed on the system and configured as the active version of the command line tools to install packages again.
Post not yet marked as solved
Further feedback:Opening Force Quit from the Apple menu is supposed to provide a shortcut to force quitting the current app. You're not supposed to force quit Finder, so the menu doesn't even open if the current app is Finder.
