I don't know if it is connected, but iOS 18 seems to generally have trouble with notifications.
Setting it to use the display as a count seems to help.
Restarting the phone or turning notifications off and on for an app sometimes helps.
jlilest
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
This forum is for people developing software for Apple platforms.
You should probably contact the software developer to ask for them to add new features to their applications.
I was under the impression that UIKit elements weren't supported for widgets.
You might get better answers in the consumer forum.
This one is for people developing software for apple devices.
https://discussions.apple.com/welcome?cid=gn-com-community-lp-get_help
That said I found a post talking about Waze putting out an emergency patch.
You might also look for support forums for the applications.
It is worth remembering that there is nothing stopping someone pointing a phone camera at the screen and recording it that way.
The name can be what you want.
It is good to have a naming convention for apps you create.
Have you considered attributed strings?
That, among many other things, supports tab stops.
I find that opening the device/simulator window and unpair the device.
It will immediately start to re-pair with the device.
3rd party vpn's can block the connection.
There is at least one Kotlin plug-in for xcode that would let you develop iOS applications in Kotlin.
I would suspect the ease/difficulty of making your apps work in iOS would depend on how you built the ui.
If everything is in Kotlin it would be easier than if you used android specific code.
The signature for the delegate method has likely changed to support swift concurrency.
That sort of issue has broken a lot of our app's screens,
Those are two different methods.
This is the one with a closure that works
https://developer.apple.com/documentation/uikit/uiapplication/1648685-open
This one, with no closure is deprecated and nonfunctional
https://developer.apple.com/documentation/uikit/uiapplication/1622961-openurl
Apple seldom does simulators for minor releases.
Those tend to not impact the simullator.
I would expect to be able to use swift 5 for some time.
xcode 16 doesn't require you to use swift 6
That said, it is better to begin migration sooner rather than later.
We still have objective c code.
It has been deprecated for quite a while.
It is worth treating deprecations as an error and start updating the code when you become aware of it.
We got hit by URL returning nil for bad url's, we internally used an invalid url for many years for internal navigation.
Waiting till it broke to fix it cost us a lot of time and work.
If you can connect to the same network as the mac is on, it should be able to see it.