[quote='760976021, rene.lv.cs, /thread/760976, /profile/rene.lv.cs'] My guess I think when the transition to the next screen happens, the reference to some critical information for save password gets deallocated and then some Apple Api tries to show the action sheet but this does not work because some Information is missing. This seems to prevent the userinteraction and some code runs in an endless loop which would explain the memory raising quickly (our production build runs normally between 30 MB and 80 MB Memory). [/quote] I'm not sure, but that sounds pretty plausible, imo. Make sure to file a bug for this and link it here.

Mac users can run unnotarized apps, but in macOS Sequoia there have been some changes that make it slightly more complex. Instead of control-clicking, you'd need to go to System Settings and allow the app to run. From what I know, you need to enroll in the developer program to notarize and distribute your apps (not necessarily via the App Store), but correct me if I'm wrong.

The key to your problem is likely code signing, but you might've figured that out already. From your description, I suspect the issue is related to this, since you're essentially not changing any code, so this is the only other thing that could fail. And indeed, we can also see that in your Console Logs: default 10:22:09.228811+0100 kernel AMFI: code signature validation failed.

You should report this to Common App too, as they might be able to address it if it's an app issue. It might be related to a null pointer dereference due to some concurrency issues (hence KERN_INVALID_ADDRESS at 0x0000000000000000 and 0 libsystem_kernel.dylib 0x00007fff206689ce __ulock_wait + 10), but I'm not entirely sure... From what I see, it seems that these concurrency issues arise when WebKit tries to load some system preferences. I noticed both of you use macOS 11.7.10 (20G1427), so perhaps it's also related to this. I did a quick search on the internet and found that other people are experiencing the same issue on the same macOS version.

Filed FB14686829. Thanks! I noticed all links in the email used df-webapp-dr-ause1.apple.com instead of developer.apple.com. Perhaps it stands for "developer forums webapp disaster recovery AU server 1" or something similar.

Sure, I will file a bug when I can. Strangely enough though, the button worked for your reply on this thread and another one I received today, so the issue might be fixed already 🤔

Are you sure you used the #if os(watchOS) condition everywhere you use CMBatchedSensorManager? I'm pretty sure that it should've removed all references. Do you use the shared class somewhere in your iOS code? Maybe that's part of the issue - perhaps a method of that class that you use on iOS uses the CMBatchedSensorManager.

I used this API a few months ago in a macOS app and yes, it had a rate limit of 50 searches per minute. That means that, after 50 searches are done in less than a minute, you'll have to wait in order to send the next requests (I believe all your other requests within that minute will fail). I haven't found any mentions of the actual rate limit value in the docs, so you should experiment with it yourself. I believe this might be the error you'll get if you exceed the rate limit.

@YoshiakiK you can file feedbacks and bug reports using the Feedback Assistant.

Maybe apple allows his own softwares Indeed, I believe that's what's going on. Safari has some special entitlements, you can see them if you run the following command in Terminal: codesign -dv --entitlements - /System/Volumes/Preboot/Cryptexes/App/System/Applications/Safari.app. The special entitlement that allows this kind of behaivor is com.apple.private.tcc.allow: [Key] com.apple.private.tcc.allow [Value] [Array] [String] kTCCServiceAddressBook [String] kTCCServiceCamera [String] kTCCServiceListenEvent [String] kTCCServiceMicrophone [String] kTCCServiceScreenCapture [String] kTCCServiceSystemPolicyDownloadsFolder [String] kTCCServiceCalendar [String] kTCCServiceSystemPolicyAppData [String] kTCCServiceAppleEvents I hope it is not the same behaviour for full disk access grant... There is another simillar full disk access entitlement value, kTCCServiceSystemPolicyAllFiles, but Safari doesn't have this. but this is not good for security... While these Apple apps have these entitlements, other apps cannot obtain them without explicit permission from Apple. They need to be signed by Apple in order to receive these entitlements. So, generally speaking, there is no way for them to access these permissions without prompting the user, unless they exploit some sort of vulnerability. If you find such a vulnerability, you should report it to the Apple Security Research website.

How do we stop users from disabling the permission incase the user has admin rights? Usually, any admin user should be able to change these kind of settings, so if you want an user to be unable to do that, they shouldn't have admin rights. Perhaps you can do something with the MDM APIs for that. Regarding your other questions, I'm unsure, but: In particular, do both the client and server need to be in the same private subnet range for the prompt to be shown? My guess is they shouldn't be on the same private network range (not necessarily subnet), but I haven't tested that. a VPN is not really a local network Perhaps the machine should still see it as a local network, especially if your machine is residing on a private network range through the VPN.

What you're looking for is the calling convetion for Objective-C on ARM64. While the ARM64 calling convention specifies that the first 8 arguments are passed on the first 8 registers (x0 through x7), there's also a notable difference between x86_64 and arm64: On x86_64, the compiler treats fixed and variadic parameters the same, placing parameters in registers first and only using the stack when no more registers are available. On arm64, the compiler always places variadic parameters on the stack, regardless of whether registers are available. If you implement a function with fixed parameters, but redeclare it with variadic parameters, the mismatch causes unexpected behavior at runtime. Source: Addressing Architectural Differences in Your macOS Code. So if a method accepts a variable list of parameters (being a variadic function), all arguments will be passed on the stack. An example of such a function is objc_msgSend.

Just like the other vulnerabilities in software used in macOS, this will most likely be fixed by updating to the newest version in the next major macOS 14 update. Here’s a recent example when other OpenSSH vulnerabilities were fixed.

[quote='758102021, saradinushi, /thread/758102, /profile/saradinushi'] their reply was to get advise reaching out to Apple support [/quote] Hello, this is the Apple Developer forums. You might want to check out the Apple Support website and the Apple Support Community forums. I'm not sure how your company data system works and how your iMessage thread appeared in a Console in SSH, but iMessage is end-to-end encrypted.

[quote='758285021, amiokumarsarkar, /thread/758285, /profile/amiokumarsarkar'] Reported this issue through feedback assistant. [/quote] It's great that you did that. I think it's good practice to also post the feedback numbers here for reference.