I'm trying to use a slightly longer more descriptive name for my app in the App Store than what is displayed on the Home Screen.
I've set the CFBundleDisplayName in the Info.plist to the shorter version I want appeared on the Home Screen. This works fine for Ad Hoc and Development builds. However, after uploading and installing through Test Flight, the Home Screen name is changed to the longer one in App Store Connect.
I found a few old questions regarding this and I'm pretty certain I have this setup correctly. I wonder if something changed recently with the publishing flow? Or maybe, this is something that only happens in Test Flight? Are there any other PList or export options I need to set to enable this? In my testing I've also verified CFBundleName and CFExecutableName are the shorter version, but doesn't seem to effect what's displayed on the Home Screen.
We are using XCode 13.2.1
Thank You!
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Starting on August 1st, the new Activation Events for Subscribers dropped to 0 in the App Store Connect Trends Report. Our App typically gets around 40 new Activations a day, and based on Firebase Analytics and the fact we see new subscribers coming in through our DB, that trend appears to be continuing. Not much has changed with our App in the last few months and everything appears to be operating normally, which makes me think this is a reporting error on Apple's end. It's also a little suspicious that it started on the 1st of the month.
It's hard to tell, but it appears Daily Subscription Sales is reporting correctly, but Active Paid Subscribers is declining, I guess because the new Activations aren't being reported?
Has anyone else seen anything similar? I'm not sure what the next steps are to debug this other than open a ticket with Apple. Thanks.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Subscriptions
Analytics & Reporting
The majority of our sandbox calls to verifyReceipt end in an ETIMEDOUT error. This is making it very difficult to verify our purchase flow for our pending release. We have not yet migrated to StoreKit 2 and still rely on this API endpoint.
The Apple API status page reports no issues.
Is anyone else encountering this?