0

I recently updated an Apple Watch App from the app + extension lifecycle to the SwiftUI lifecycle.

Or to put it another way, the bundle Ids have changed so that:

Before

  • com.myapp
  • com.myapp.watchkitapp
  • com.myapp.watchkitapp.extension

After

  • com.myapp.paddlelogger
  • com.myapp.watchkitapp

For me everything works great, but we have multiple reports of people seeing two versions of the app in the Apple Health Sources

Screenshot of multiple app sources in Apple Health

This means there are two "sources" of data and two sets of permissions. In the past we just had one set of permissions.

It also means we have trouble reading data on the iPhone app that was recorded on the watch app.

HKSource.default().bundleIdentifier is com.myapp on iPhone and com.myapp.watchkitapp on Apple Watch

That must be part of the issue(?).

Is this something I've done wrong? I can't find any docs on migrating from from the legacy Extension style to the new SwiftUI Lifecycle

lewis
  • 2,936
  • 2
  • 37
  • 72
  • Can you raise a ticket with Apple TSI (DTS team) and they should be able to help you. You will be entitled to 2 tickets per year, you can buy more if you exhaust them – user1046037 Nov 06 '22 at 19:36

1 Answers1

0

Workaround: When reading Apple Health data in the app I now have to check for both bundle ids to distinguish data from my app vs that from 3rd party apps.

From speaking to other developers, this is not the only app that appears twice in Health, so I am assuming this is an Apple issue.

lewis
  • 2,936
  • 2
  • 37
  • 72
  • Is there any update on this issue? Only I'm seeing it too and it's causing issues with my app users. Have also put Feedback in (FB11704560, submitted 4 months ago) and have a TSI request in. Thanks – Simon Feb 02 '23 at 08:53
  • Hi Simon, no update :( my work around is in place and I haven't really done anything with it since, although I spoke to someone who works for a big fitness app yesterday and they said they are seeing the same issue. please do update here if you get anything back from Apple – lewis Feb 03 '23 at 14:38
  • 1
    Will do. Only update is I also put in a TSI request and got rejected as it's a "known issue" so at least they are aware. – Simon Feb 04 '23 at 11:37
  • 1
    it's a shame you have to use TSI's get apple to confirm the existence of a bug (or really communicate with you at all), but better than nothing I suppose – lewis Feb 07 '23 at 11:19