Posts

Post not yet marked as solved
2 Replies
Not working for me in Xcode 14.1 RC
Post marked as solved
15 Replies
I figured it out. I had a new image which was a pdf. If I change tick the "Resizing: Preserve Vector Data" box in the asset catalog it works. With it unticked I think it must go over some resource limit and get killed. To figure it out I replaced all my parent live activity/DI views with simple text fields and then it worked. Then it's a case of adding thing back until you figure out what's over the limit. Obviously it would be better if apple fed this back to developers in a clear way. And also if the sim more closely modelled the device.
Post marked as solved
15 Replies
I'm seeing the same thing, I've raised feedback FB11699078. I also bought it up in the slack chat that Apple hosted yesterday. No reply as yet.
Post marked as Apple Recommended
Post not yet marked as solved
3 Replies
I assume you are seeing this issue when archiving your code? Is it an error or a warning? I have an issue where images are not showing in my widgets, I'm wondering if this is related to what you are seeing or not. Probably not as I can't find any messages like this, but also can't figure out why the images wouldn't load. Everything on the watch is so much more painful than the phone.
Post not yet marked as solved
8 Replies
I'm on Xcode 14 beta 4. I created a new empty watch only app and then a widgets extension. I see the build error that yvsong mentions above. Then I run the terminal command that colejd recommends and that removes the build error. But I still don't see a widget preview, I just see a black rectangle. I tried changing the text color and removing the date formatting and just making it a string, I still just see the rectangle. I love this new combined framework so much. Can't wait to build some cool stuff with it.
Post marked as solved
9 Replies
I see crashes for this too, and in production not just TestFlight. If anyone ever finds a solution or how to debug further please share 🙏
Post not yet marked as solved
1 Replies
I've used https://github.com/RobotsAndPencils/XcodesApp/ to go back to beta 2. not tried it in beta 3 watch development on a production apple watch is not really possible for me, it's just too slow to be worthwhile
Post not yet marked as solved
4 Replies
With iOS 14 I notice that when you delete an app instead of offering to delete your health data it shows an option to go into the health app where you can delete your data. That screen also shows permissions. It would be very helpful to be able to deep link to that screen for users who change their mind about what permissions they want to grant. "How do I change my health permissions?" Is a common support request for us. Anyway, the above change implies that such a link/url does exist. I wonder if anyone knows what it is?
Post not yet marked as solved
8 Replies
I haven't tried this with the new widgets, but with the old widgets I found that the widget core data instance was very slow to receive updated, as in days later. This issue was true in watchOS for a while and then it was resolved, so it may be resolved in iOS 14 too, but just something to test for. (The workaround in my case is to store the database in a shared container)
Post not yet marked as solved
6 Replies
I think Apple is still deciding what this number should be and it is changing between betas. My hope is that at least a few times an hour should be possible.
Post not yet marked as solved
2 Replies
Yes, I am seeing this a lot, both with my own widgets and ones provided by Apple.
Post not yet marked as solved
2 Replies
I don't work at Apple so my word isn't canonical, but my instinct is that the fact that onAppear is working is a bug. The widgets are totally static, you should imagine that they are generating a still image which is shown the user at the system's discretion. Much like the app switcher screens, or launch screens. They can't take any action on being shown or hidden, or under any other circumstance.