Post not yet marked as solved
We are relying on ASWebAuthenticationSession to do web authentication.
Since the API doesn't support POST requests directly we have to generate local file in ~/Library/Application Support/<foo.bar>/WebAuth.html containing the POST and use initial URL as file:///Users//Library/Application%20Support//WebAuth.html
Problem is that Safari sometimes pops a dialog "Confirm the file to load" and sometimes it doesn't. This doesn't depend on "Full Disk access" TCC.
Does anybody know a way to prevent this from happening? MDM option or something?
Also styling of the popup is a rather poor UI choice - looks very confusing and like the user may choose another file to load.
Chrome f.e. doesn't do such popups.
I already have FB13340210 for this.
Post not yet marked as solved
On iOS we are trying to log energy use by our network extension to help us isolate troubled areas. task_info with TASK_POWER_INFO_V2 does return task_energy value and it's growing over time, but it's not clear what exactly it means and how it supposed to correlate to battery usage screen from iOS settings.
Does anybody know anything about this?
Post not yet marked as solved
When we call ASWebAuthenticationSession with preferEphemeral = false macOS generates this dialog with a meaningless "(null)". This looks very odd and scary for a normal person. Why it shows "null" and can we control this to make it meaningful at least?
Post not yet marked as solved
Seems like gethostname() is not returning host name anymore in iOS 17 beta, just localhost. Is this a bug?
Hello.
Does WKWebView on Mac support FIDO2(webauthn)?
We need to implement this in our app and ASWebAuthenticationSession API comes up in searches all the time as the only solution. Is this still the case?
From my experiments ASWebAuthenticationSession on Mac doesn't provide best user experience - too much fiddling and odd behavior for an end user.
F.e. user needs to click Open button from the browser window to pass token to the very same app which initiated the window and this is not very logical considering all the efforts to setup applink.
Would appreciate an advice.
Post not yet marked as solved
We've got an uncaught C++ exception caused crash. Two versions of the same product, one is arm64 another is x86_64, same bug, same crash, two reports.
One from arm64 has a message
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 0
Date/Time: 2023-01-26 09:23:24.8975 +0200
OS Version: macOS 12.2.1 (21D62)
Report Version: 12
Crashed Thread: 18 Dispatch queue: NEFlow queue
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
terminating with uncaught exception of type std::__1::regex_error: One of *?+{ was not preceded by a valid regular expression.
and another one doesn't
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 0
Date/Time: 2023-01-26 05:40:35.2732 -0500
OS Version: macOS 12.5.1 (21G83)
Report Version: 12
Crashed Thread: 19 Dispatch queue: NEFlow queue
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
The first one is immensely helpful just because of the reference to std::regex and another one is close to useless. Crashed thread is identical in both cases:
0 libsystem_kernel.dylib 0x7ff80ef6300e __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff80ef991ff pthread_kill + 263
2 libsystem_c.dylib 0x7ff80eee4d24 abort + 123
3 libc++abi.dylib 0x7ff80ef55082 abort_message + 241
4 libc++abi.dylib 0x7ff80ef461a5 demangling_terminate_handler() + 242
5 libobjc.A.dylib 0x7ff80ee42e19 _objc_terminate() + 104
6 libc++abi.dylib 0x7ff80ef544a7 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x7ff80ef54458 std::terminate() + 56
8 libdispatch.dylib 0x7ff80ede232b _dispatch_client_callout + 28
9 libdispatch.dylib 0x7ff80ede8317 _dispatch_lane_serial_drain + 672
10 libdispatch.dylib 0x7ff80ede8dfd _dispatch_lane_invoke + 366
11 libdispatch.dylib 0x7ff80edf2eee _dispatch_workloop_worker_thread + 753
12 libsystem_pthread.dylib 0x7ff80ef95fd0 _pthread_wqthread + 326
13 libsystem_pthread.dylib 0x7ff80ef94f57 start_wqthread + 15
There is no mentioning of string "regex" anywhere else in crash logs in backtraces or remaining parts. So the exception message here is the most important piece of information and yet it's mysteriously missing in one crash log and present in another.
Any idea why the very same exception message is not always logged?
We are working on a Network Extension based iOS app.
Is it possible to have an app proxy (for per-app VPN) and packet tunnel providers within the same extension binary on iOS? On Mac this seems to be allowed, but with iOS it looks like we have to separate binaries - one per provider. In our case this complicates things.
tandre.