On our last update we started getting user reports for this same error (AssetErrorDomain 6). Strange thing is we've been using ODR for a while now and only started receiving these reports with our last update. It does only seem to happen to users that update rather than fresh install and we also can't reproduce in Test Flight. One thing that changed with our release is we finally switched from the Legacy to new XCode build system. Could that be related? I also wonder if it's just a transient issue on Apples end? I've read some people suggest changing the tags with every release. Seems like that'd work, but it's a kinda ugly work-a-round.

I figured this out. Turns out I misdiagnosed what was going on. It is using the CFBundleDisplayName for the Home Screen Icon. However, it's getting truncated when uploaded through Test Flight because Test Flight adds the little blue circle next to the name which pushes the length over the limit. When the App is released and the blue circle goes away, it fits. I imagine this will also happen after app updates, which also adds a circle next to name. I misdiagnosed this because both the CFBundleDisplayName and App Store Name started with the same 11 characters.

This has been our top crash as well for sometime. We've never been able to duplicate it. Interestingly, we only have reports on iOS 10 - 14. Perhaps Apple fixes it in iOS 15?

I believe you will need to rebuild the older version with a higher version number than the live release and re-upload to App Store Connect. App Store Connect will not allow you to upload a build with a lower version number than the current release. You can see in App Store Connect - Create a new version, step 3 requires incrementing the version number.

We are experiencing the same issue. I filed this forum post a few weeks ago (https://developer.apple.com/forums/thread/712921) and opened a Feedback Request. Still no response from Apple. Our Activations dropped to 1 on August 1st and then 0 for the remainder of August, very similar to what you are seeing. We still see plenty of valid Activations come through our DB and Firebase Analytics. It's very unnerving, but it's a little reassuring to see it happen to someone else. I've double checked our subscription flow a million times even though nothing changed on our end in August. It sure looks like a reporting issue on Apple's end.

Just to provide an update. The support ticket we sent through https://developer.apple.com/contact/topic/select Reports and Payments has been slowly escalating through App Store Connect Support and is now being reviewed by engineering. They warn it could take a while. To demonstrate the issue we sent Subscription Events and Sale Events Reports. In our reports we clearly see many New and Renewal Sales events with no corresponding Activation or Renew Subscription Events. One other interesting detail is that it only appears to be happening to a subset or our SKUs. The SKUs that we do get events for are older and have shorter IDs (e.g. monthly). The SKUs we do not get Subscription events for are newer and have longer IDs (e.g. com.company.app.monthly). It seems unlikely to me that the format of the product ID could be the issue, but who knows? It could also be that it only happens to people that subscribed somewhat recently? I'll post another update when I have more information.

I encountered the same issue, but it only happened on our iOS 12.1 device. I did a few Test Flight builds last week, which work fine, then did a couple this week that fail to launch on the iOS 12.1 device. It works fine on our other test devices. Very little changed between the builds and Ad Hoc builds work fine. I suspect it had something to do with bitcode processing, but I never really go to the bottom of the issue. I updated that test device to 12.5.6 and the problem went away. I figure if our real users encounter this, it'll be a pretty small subset and they can upgrade their OS to resolve it.

We had a similar situation. As understand the docs, removing an item for sale will end the subscription for current subscribers. Obviously, we did not want to do this. For our case, we stopped presenting the legacy SKU in our in-app UI. We also raised the price for new subscribers to discourage people from switching to it within the App Store UI. We do continue to support it though if they do. I'm not sure if there's another approach, but this worked for us.

For anyone following this issue. Our issue was resolved around Oct 19. I haven't heard from Apple exactly what happened or what they did to fix it, but all of a sudden Sales and Trends report seems to accurately reflect our active subscriber counts.

@gbesler, are you still suffering from this bug? Our issue was magically resolved around Oct 19th. I have no idea what Apple did to fix it, but at least we seem to see accurate active subscribers counts again. We were in the dark from between August 1 - Oct 19.

After a few days the issue magically resolved itself :shrug: Maybe posting this forum resolved it!