I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch again, there is no any response when tapping the app icon. I managed to export some system logs by installing a sysdiagnose profile, and this info looks suspicious
Could not launch app on watchOS downloaded from TestFlight
https://mastodon.social/@brianmueller/116564966499241821
There are some +1 replies to this post.
So far, I'm aware of this issue affecting CARROT Weather, Overcast, Pedometer++, and Parcel.
For what it is worth - there seems to be no difference between Internal vs External testing behavior (i.e., having an "Approved" Test Flight version did not seem to make a difference for me).
Not that anyone proposed there would be a difference, but I thought I would try it in case there was a difference in behavior.
The "immune" TestFlight users are still interesting to me.
There are people who it never happens to, and others who get it frequently.
My sample size is 10 people. 5 hit, 5 "immune".
In the 5 immune, 3 have Apple Watch Ultras. In the 5 hit, none have Apple Watch Ultras.
99% likelihood that it's just coincidence...
But I wonder if Carrot or one of the bigger TestFlight beta's can see any patterns in watch models with a larger sample size?
@tph I think it is coincidence... At least three Ultra users are still affected in the company
@tph But "immune" users do exist Just not sure if it is real immune, or just a matter of time😄