“Visual Studio Maui IOS”

If I display CallKit immediately after receiving the callback, and then the function returns, but the call ends within 7 seconds, will the second check be considered a misuse? No. The second check is actually validating whether a call has been reported, not whether it's still active. I'll also say that both of the checks here are designed to be more generous than the API contract specifically requires, just to minimize the possibility of any incorrect termination. There were a small number of issues [1] with this code several years ago, but I haven't seen any problems with it since. [1] All of the issues tended to involve fairly odd edge cases/circumstances. For example, there was an issue (fixed in iOS 14) with the exact timing of the secondary check where JUST the right timing between an incoming push and reporting/ending your call could cause the app to crash. Triggering this bug required continually repeating the push -> report call -> end call cycle at a cadence of ~7s for several hours. T

App installs but won’t launch on iPhone: “profile has not been explicitly trusted by the user” My app builds and installs on a physical iPhone, but it will not launch. Setup: Flutter 3.38.7 Xcode 26.3 iPhone 15 Pro Max iOS 26.3.1 Exact error: ERROR: The application failed to launch. (com.apple.dt.CoreDeviceError error 10002) Unable to launch com.sherpa-map.routestudio because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. (FBSOpenApplicationErrorDomain error 3) The confusing part is that on the iPhone, Settings > General > VPN & Device Management only shows VPN and Sign in to work or school account, so there is no obvious developer trust option to tap. Is this a current iOS/Xcode issue, or is there a new trust flow for developer-signed apps?

same thing here. here is what I have tried: Tested on iPhone on both Wi‑Fi and cellular: same failure. -Checked iPhone Settings → General → VPN & Device Management: no developer cert/profile shown to “trust”. Regenerated signing in EAS: Ran eas credentials -p ios (logged into Apple Developer team) Deleted/revoked the existing Apple Distribution certificate Let EAS generate a new Distribution certificate and new Ad Hoc provisioning profile including the iPhone UDID. Rebuilt multiple times after credential reset: Verified the iPhone UDID was included in the ad-hoc profile by re-selecting devices Ran eas device:create (Website flow) Rebuilt and chose “No, let me choose devices again”, selected the target iPhone. Checked Apple verification endpoint reachability from iPhone: https://ppq.apple.com intermittently returned 502 Bad Gateway, later returned ok. Checked EAS build list and ensured installing the latest build ID from March 10, 2026 (not older IPAs signed with the revoked cert). Noted possible

Same problem. I've been dealing with this all day, until GPT told me about this thread. Mine is a Flutter project. I get The application could not be launched because the Developer App Certificate is not trusted. from Xcode, and Unable to Verify App in iOS.

Perhaps I didn't explain myself well. I wasn't making assumptions about how the the APIs operate - the only thing I was claiming (well trying to) was that paths provide the concept of file location and in certain contexts that concept matters to GUI apps (with the NSBrowser example being an obvious one). Sure. And, to be clear, I don't mean that paths don't EVER have a place and/or aren't a good solution. However, I do think those use case are more limited then they seem and that most interactions with files are better handled through object references (which are tied to a specific file system object), NOT paths (which describe a location in the hierarchy). Our APIs don't do a very good job of expressing that idea, but APIs like reference URLs and bookmarks are actually object reference APIs, not just weird ways of storing paths. Very interesting. Yeah I use that (watch root) With the watch root flag set it does seem to just track whatever is at the path. Ahh... Yes, you're right. It's been awhile since I loo

It would be helpful if we could get a bug report with attached logs from both Mac and iOS. Please see our instructions for capturing Core Device logging for both platforms and attach the collected logs to your report, and then post the FB number here. — Ed Ford,  DTS Engineer

Per the Xcode 26.3 Release Notes, Xcode 26.3 supports on-device debugging in iOS 15 and later. iOS 12 is no longer supported target for running your app with the debugger attached.

There is no difference in behaviour. Please send us the transaction ID of the two transactions via a feedback assistant ticket to investigate further. Thank you How to File Feedback assistant ticket? https://feedbackassistant.apple.com/ Login with your developer account, Choose iOS & iPadOS” Choose AppStore “Incorrect & Unexpected behavior Input the issue description and title. Upload attachements Click “Submit” Copy the Ticket ID “FBxxxxxxx” and let us know.

Same issue in SwiftUI while using .keyboardType(.numberPad) in combination with .preferredColorScheme(.dark). I'm afraid it's iOS / iPadOS bug.

Thanks for the post. Very interesting question about that API! What do you mean for staleness check? Once a Network Extension is installed, authorized by the user, and saved to the system preferences via its respective manager, the configuration is owned by the OS. The OS will continue to invoke the extension binaries as needed, regardless of whether the main app has been force-quit or hasn't been launched in months. I’m interested on the behavior you are seeing is almost certainly caused by a secondary factors. Has the user has offload unused apps? I believe when an app is offloaded, its extension binaries are deleted along with the main app. The VPN profile or Hotspot configuration will still appear in iOS Settings, but the OS will silently fail to invoke the NEHotspotHelper or fail to connect the NEPacketTunnelProvider because the executable no longer exists. You have mentioned 90 days? If this app is being distributed to internal testers or beta users via TestFlight, the app and its extensions wi

@bocallaghan We are expecting this issue to have been resolved in the latest versions of iOS 26. If you are still encountering this issue on iOS 26.3, please update your Feedback Report indicating the version you are running, and any other information, and if possible, new logs please. If you are indeed encountering the problem with 26.3 still, we would appreciate if you can also gather diagnostic logs from the affected device and attach it to your feedback. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then, once the logging profile is installed, reproduce the problem, keeping track of the actual time of the actions you take and the result you see. Once the problem is reproduced, follow the instructions at the above link to trigger a sysdiagnose as soon as possible to allow for the most detailed log entries to be saved. Please let me know when you have done so