Start here: TN3111: iOS Wi-Fi API overview. Especially note this part: iOS does not have a general-purpose API for Wi-Fi scanning and configuration.

Start here: Connect to the Find My network.

Apple probably doesn't consider this a bug but I filed FB14378568 anyway. Did you frame it as a bug report, or as a feature suggestion? It’s definitely not a bug, since of course an “undocumented API” is no API at all. But lots of developers probably would concur with a suggestion to add proper APIs for these examples and others. You could call for others to submit their own suggestion feedback and reference your FB number.

What you need to use is described here: In-App Purchase. Now there’s very little Capacitor discussion on this forum, but a quick search did turn up this which may help you get started: https://capacitorjs.com/docs/guides/in-app-purchases

Here’s one take: Apple’s Human Interface Guidelines. Learn it. Know it. Live it.

AccountCreationData(name: "name", email: "email", phone: "phone", password: "password") 110 bytes Something is off. Testing here, if I encode your struct with those exact values, the result is 69 bytes, not 110 bytes. Can you print out a string representation of the encoded JSON? And separately, do you need to set a Content-Type: application/json header so your server knows that the body format is JSON?

You just need to change one or both of those parameter names in your code. The argument labels (didSelectTab and previousTab) are part of the method signature and need to match the protocol declaration, but the parameter names can be whatever you want. I’d recommend this: func tabBarController( _ tabBarController: UITabBarController, didSelectTab selectedTab: UITab, // better parameter name previousTab: UITab? // no custom parameter name needed ) (Or you can omit tabBarController and selectedTab entirely if you don’t actually use them in your code.) Also consider entering a Feedback to report that the method declaration in the SDK is poorly formed. Presumably your error came after letting Xcode auto-generate the method for you based on its declaration. So it would be better if the SDK declaration were formed like my proposal above.

Can you post a full crash report? See Posting a Crash Report. But also can you post a small snippet of code that demonstrates the problem? Can you narrow it down to any specific property on your encodable type?

The accuracy properties are basically all you have to work with. There is no API to get lower level information. See also this thread.

For one thing, the network name can leak location information. Some users may not want to disclose that they are connected to a network named something like “No-Tell Motel Free Guest Wi-Fi”.

See the Apple-recommended answer in this thread.

Do you happen to have results from the REST API for the same locations? Could be interesting to compare them. Any idea if the unit has changed? The documentation does say it’s kilometers per hour, but that’s not really meaningful since any Measurement value is self-describing. But could be interesting if the unit has changed but not the raw value, or vice versa.

Xcode is now useless for programming. Actually you can fix this easily. Go to Settings → Themes → Source Editor and change Documentation Markup to a monospaced font.

I also tried to contact my bank. They say on their side everything is working fine with the iOS app. If their app is falsely claiming that your device is jailbroken, then it’s a bug in their app. There’s nothing anyone at Apple or on this developer forum can do to help. Any idea guys? Is there anything I can „reset“ somewhere? If I were in your end-user shoes, I’d delete the app and reinstall it so that it there is no saved or transferred data.

Actually my guess is that the app (not the OS) stored a “this device is jailbroken” flag in the app’s settings, and then never actually checks again to see if the device has become non-jailbroken. This flag would be part of the app data that gets transferred to a new device or restored from backup. If it never actually checks for jailbreak again, then you will be stuck like this forever or until you uninstall the app to delete its saved settings. And if your device isn’t jailbroken, then it’s a bug in the jailbreak detection that gave a false positive in the first place.