Apple Maps Guides

So, first off, there are two critical details I need to clarify: Note in MAC OS everything (same DExt and UserClient-code) works fine in the background and in the foreground. macOS doesn't implement any of the app suspension semantics iPadOS does, which means you can't really compare the behavior of the two systems. That leads to here: 1 variation A) UserClientApp has attribute [Background modes][Enable external communications]. The external-accessory background mode is totally unrelated to DriverKit and isn't actually doing anything in your app. It allows apps using the ExternalAccessory framework to communicate with their accessory in the background, but that framework (iOS 3.0) and the background mode (iOS 4.0) are MUCH older than DriverKit. Making this as explicit as possible: B) A way to pursue Apple-store to accept (without MFI) an UserClientApp with [Enable external communication]. ...adding external-accessory is not changing ANYTHING about how your app wakes/sleep in the background. You will

Following up with this to clear up some odds and ends: Provisioning profile ... doesn't match the entitlements file's value for the ... userclient-access entitlement. One thing to be aware of her is that Xcode has a bias in the way it presents codesign errors where it assumes the Entitlement.plist is correct and the profile is wrong. However, in practice that's basically never the case with DriverKit entitlements and tends to lead to a lot of flailing trying to somehow fix the provisioning profile. This error ALWAYS means that the entitlement.plist doesn't match the profile. You fix that by: Changing the Entitlement.plist to match the profile. Changing the actual profile. That means either: Submitting a new request to correct any mistake (this case). IF you have been granted multiple instances of the same entitlement, then you switch to manual profile generation and manual codesigning. See this forum post for more details on that flow. However, the key here is to understand that this: ...our hypothesis is tha

You should check with the support resources provided by the 3rd party to get assistance with their software. Do Rork.com has a support channel? Are you able to demonstrate the issue in a test project created from one of Xcode's templates, and using only Apple APIs? Unless another developer in the forums has experience with the third-party and can provide assistance. Albert Pascual
  Worldwide Developer Relations.

Are you able to demonstrate the issue in a test project created from one of Xcode's templates, and using only Apple APIs? If not, you should check with the support resources provided by Flutter to get assistance with their software. You can find tips on creating and sharing a test project in Creating a Test Project. Unless another developer in the forums has experience with the third-party and can provide assistance. Albert Pascual
  Worldwide Developer Relations.

BTW, I can put a toolbar at the bottom of the window, but it isn't separated a fixed distance from the window like Safari's is. From my reading of Apple's HIG on toolbars, this is the proper place to put toolbar items in visionOS. Should I go with this design (which looks like Apple HIG's preferred design) as opposed to following Safari's design? struct ContentView: View { var body: some View { Text(This is some text) .toolbar { // .bottomOrnament only placement that works ToolbarItemGroup(placement: .bottomOrnament) { Button(Hello) { print(World) } Button(Goodbye) { print(cruel world) } } } } }

@Matt522 Make sure you file a bug report using Feedback Assistant. Apple needs to know that this affects people's apps. Be sure your bug report includes a simple app that demonstrates the issue.