Our system pushes message to iOS app three times a day(per 75k at a time,total 230k a day).
For example, at 27 March 2019, we pushed 230k to Firebase, and Firebase returned about 220k for "Success"(we count this number in our system and it was normal at this step). But in Firebase Website, we saw Firebase sent only 170k to app(according to the picture). And at this day, we saw iOS app activeness which was reduced 20% according to our system.
And at 3 April 2019, we saw Firebase sent only 98k to app! This Problem appeared everyday until now and we did not change any push code. It is strange!
Can you tell me what is happenning when Firebase pushes the message to app? Why it reduces quite a few? Did the problem relate to the SDK version or certificate update or PHP push parameters? Do you have any Error Log for the problem? I am confused. Please help me! Thanks!
Related
I'm facing a really random error that I cannot debug, for the life of me. I've tried everything, so I'm really hoping someone here can help.
I've created a React native app for iOS and Android, and I'm using FCM for data messages and notifications.
Specifically, I'm using topics to send notifications.
Here's the weird part:
It works sometimes and sometimes it doesn't. This is across different users and different topics. I will get a notification for a topic I've subscribed to one day and the next day, I won't get a notification sent to the same topic.
Some users will get a notification and some users don't. And they are all subscribed to the same topic.
There are no error messages. I assume this is something to do with FCM? I am at a loss on how to debug since it's so random.
Any suggestions?
I'm almost ready with developing my first windows phone app. Can anyone tell me how long it will take to get the app in the store. For ios apps the apps must be approved, that usually takes about a week, for Android it usually takes only a couple of hours. How is it for Windows, does Microsoft approve the app?
Second question: I need a url for the app that refers to the windows app store?
Is the url known in advance or do I have to publish first before I know the exact app store url of my app?
Thanks for the help!
First question: At this moment it is around 3 to 4 hours for a republish and a day for normal a full publication. Just submitted an app last week. These times can change, one of my (new) apps was through the publication in 1 hour. Do keep in mind that it can take some time before you see it in the stores (up to 24 hours)
Second question:
When you submit your publication you can see the url of your app.
I have recently published my first Mac app onto the Mac App Store, forgive me if this is a stupid question but i can find no place on iTunes Connect that shows the analytics for it, the App Analytics section on iTunes Connect only shows my iOS app? There must be somewhere to see how many units i have sold?
So i contacted apple an there reply was:
App Analytics is available only for iOS developers at this time, and it reports data only from customers using iOS 8 and above. Therefore you will not see data from your Mac app.
If you would like, I can submit feedback on your behalf for a possible future enhancement. If this is something you would like me to do, please reply with a clarification of your request, and I will be happy to send it up for you.
So the short answer is there is nowhere for you to find how many downloads/revenue you have earned. Which is well, shit
I've updated my iPhone app to support the iPhone 5 screen..
I've done this before for another app and I was forced to upload new screenshots taken with the iPhone 5.
This time however, iTunes Connect just displays the status as "waiting for review" and isn't mentioning anything about the screenshots..
I'm slightly worried something has gone wrong? App works great on iPhone 5 and simulator though.
It turns out Apple can block apps during the review process that have something wrong with metadata. If they decide your metadata is wrong they'll just change your app's status to "Metadata Rejected".
Here's the quote from the rules for this status:
Appears when specific metadata items aside from your binary have not
passed review. To resolve the issue, edit the metadata in iTunes
Connect and your existing binary is then reused for the review
process. You receive a communication from App Review in the Resolution
Center regarding the reason for the metadata rejection.
When things change to the AppStore (Apple adds a device) they might require you to get new screenshots. But if nothing changed in their system, it's normal that they don't ask.
Don't worry!
They copy over the screenshots from your last version of the app (or is your Retina4 screenshot section in itunesconnect empty?). So if you don´t want to update them, it should be okay like this.
Chances are your app has not hit review (and now as of the 21st) and won't be reviewed until after the 29th. Once your app hits review, it will become rejected for the missing screenshots. If you want to save yourself some time and pain, update the screenshots while Apple is on their downtime for the Christmas holiday. You'll thank yourself later.
My app got accepted yesterday, no word about the screenshots.
App works fine on iPhone 5, mailed Apple to complain this probably is a bug (iTUnes Connect does not recognize localized Default.png, which is what is checked to verify it is iPhone 5 optimized I believe.)
My first App is in the App Store since one week now and it is still recieving Test iAds. In the iAd network it says "Live Ads". And i have the App Store app not the xcode version. In iAd Network it says
eCPM 0.00%
Requests 450
Impressions 19
CTR 0.00%
Revenue 0
I dont know what all that stuff means, and I have no idea why its not working!!
Link to App(its free): http://itunes.apple.com/us/app/canada-taxes-tip-calculator/id449443981?l=de&ls=1&mt=8
Have you checked on other devices running it? If your phone is running an iOS beta you will only see test ads, even from app store apps.
As I've answered here, these things take some time to propagate throughout the system. Try contacting Apple and see what they can do.