@victornunez Hey Victor! New Xcode Device Hub broke Appshots ๐ญ
You got me addicted to appshot โ Codex โ problem solved, and now I have to live without it. Please save us ๐
@imeronn@expo For context, our integration includes local native patches. Cold relaunch and longer idle scenarios still need testing. Happy to share the relevant logs and patch details!
Also, are you planning to migrate the library to Expo Modules API 2.0?
Thanks again for the update!
@imeronn@expo Our initial 30-day sync also dropped from roughly 75 seconds with our previous Kingstinct integration to 34 seconds with the current setup. Thatโs a substantial improvement for us, although it isnโt a controlled SDK-to-SDK benchmark.
@imeronn@expo One later update was delayed until we reopened the app. HealthKit had requested a background launch, but iOS kept the app suspended; system logs also showed rate limiting.
@imeronn@expo The early observer registration and completion handler changes are exactly what we needed. Iโll test background relaunch โ HealthKit read โ server upload on a physical iPhone and share results and logs.
Is there anything specific youโd like me to test or capture?
@imeronn@expo Thanks for shipping this! ๐ Iโm trying it out in our React Native / Expo fitness app.
We currently use Kingstinctโs Nitro-based HealthKit library. We couldnโt get background sync working reliably even with a custom native patch, so we ended up disabling it.
@imeronn@expo Hey! How does this handle HealthKit background delivery when iOS relaunches the app in the background? Are observers registered before JS starts, and is the completion handler held until async processing finishes? Have you tested that flow on a physical device?
@thsottiaux@RileyRalmuto Quick question: I have a reset sitting in Codex right now. If I donโt use it, does it get applied automatically, or does it just expire?
If it just expires, itโd be great if unused resets could auto-apply instead of going to waste.