I have released the first version of my app a couple of days ago & it was available on app store search. I have rolled an update with some bug fixes a day later & the updated version got the status "ready to sale" and was available in app store updates within 6 hours.
But the strange thing i have observed is that, the app was only available from the standard link and was not appearing on app store search.
People were able to download the app using the link but it wasn't showing up on search (even after using the exact name). Any help would be highly valued and appreciated !
PS : when i rolled an update, i changed the keywords and category of the app to more relevant ones.
There could be many reasons for not showing up into the search results. Here are few explained :
May be the ASO changes you have done are not reflected yet so it will not appear in to search. In that case you should wait for 24-48 hours to let things go & settle
Another major & important reason is if App name you are using is very common or already is too much use in other similar apps which already are in the market before your release than also it will put your app far back into the search results that even don't show in limited search results
ASO factor will also effect your app to not appear into the search results. May be you should use more strong keywords which can help your app to compete with other similar apps. You can try & use ASO tools for that.
Last but not the least some times apple has some inner maintenance works which they do silently also affects sometimes to the search results
So from above points the solution is :
Wait for the few hours at least 48 hours to let crawl your ASO keywords & lets get effect in to search result improvements
If it not works since 48 hours you should appeal to apple review team for the same.
Hope it will work to everyone.
Related
I have been developing an iOS app that utilizes the CloudKit feature available for Apple Developers. I've found it to be a wonderful resource, especially since the very day I started designing my backend, the service I was intending to use (Parse) announced it was shutting down. It's very appealing due to it's small learning curve, but I'm starting to notice some annoying little issues here and there so I'm seeking out some experts for advice and help. I posted another CloudKit question a couple days ago, which is still occurring: CloudKit Delete Self Option Not Working. But I want to limit this to a different issue that may be related.
Problem ~ Ever since I started using CloudKit I have noticed that whenever I manually try to edit (delete an entry, remove or add part of a list, even add a DeleteSelf option to a CKReference after creation), and then try to save the change, I get an error message and cannot proceed. Here is a screenshot of the error window that appears:
It's frustrating because anytime I want to manipulate a record to perform some sort of test, I either have to go do it through my app, or just delete the record entirely and create a new one (that I am able to do without issue). I have been just working around this issue for over a month now because it wasn't fatal to my progress. However, I am starting to think that this could be related to my other CloudKit issues, and maybe if I could get some advice on how to fix it I could also solve my other problems. I have file numerous bug reports with Apple, but haven't received a response or seen any changes.
I'd also like to mention that for a very long time now (at least a few days), I've noticed down in the bottom left hand corner of my Dashboard that it is consistently saying that it's "Reindexing Development Data". I remember at first that wasn't an issue, I would get that notification after making a change but it'd go away after the operation is complete. Now it seems to be stuck somewhere inside the process. And this is a chronic issue, it's saying this all the time, even right when I log into my dashboard.
Here is what I'm talking about:
As time goes on I find more small issues with CloudKit, I'm concerned that once I go into production more problems could start manifesting and then I could have a serious issue. I'd love to stick with CloudKit and avoid the learning curve of a different service like Amazon Web Services, but I also don't want to set myself up for failure.
Can anyone help me with this issue, or has anyone else experienced it on a regular basis? Thanks for the advice and help!
Pierce,
I found myself in a similar situation; the issue seemed to be linked to Assets; I had an Asset in my record definition. I and several other I noted reported the re-indexing issue on the apple support website and after about a month it eventually disappeared.
Have you tried resting your database schema completely, snapshot the definition; since you zap it completely and than reset, see inset.
Ultimately I simply created a new project, linked it to cloud kit and use the new container in my original app.
So I'm making an iphone application that needs to scrape a website once everyday.
What I'm going to scrape is a table of upcoming games for that same day for a soccer division. Thats why i need the app to scrape from the same page and same table once everyday to keep the upcoming games updated.
I was referred to import.io but they didn't have something like a schedule re-crawl.
I would love to get some ideas and tips to how i should do this since I'm stuck now.
You might take a look at https://www.kimonolabs.com/
I played around with the service a while back and was impressed with how easy it way to set up. They have a "free" option so long as the APIs you create are not private.
Oh, and I agree with Paul, screen scraping is not something the iOS client should be doing. Too fragile, and when (not if) something breaks, you will need to go through an Apple review process to fix it.
This doesn't seem like something an app should do, your server should do it (so that the scraping is only performed once), and your clients can retrieve it from your server. That also means you could send out push notifications for important fixtures etc. Maybe that's what you meant, anyway.
If it's on the server you can just setup a scheduler (in Java, for example) to run once every x hours (probably a smaller number than 24 assuming you don't know when the website is to be updated). Then your app can just get the latest list of fixtures from your server on startup, pull-to-refresh, etc. Presumably someone will open your app, look at the fixtures, then come out of your app - so it doesn't seem like you need to cover the case where someone is in your app all day, but if you did you could use NSTimer to run every x minutes after the initial on-startup server call.
I'm not very informed on ios news, but I've looked everywhere the last few days and can't seem to find a definitive answer for the latest version of ios: Is it possible to retrieve a list (or simply the last) phone number dialled? The docs (coretelephony) mention a CallID but I'm guessing that the most you could do with that is distinguish between two different calls. I've noticed many blog posts/stackoverflow questions mentioning accessing a call log database, however from my own tests and from what I've gathered that no longer works in the latest versions of ios (infact all of the posts are dated at least two years ago). Thank you very much.
No. There is no access to phone numbers or dialing, due to security reasons. But, you can get info on the connected Carrier, etc.
I would like for my app (a single SKU) to provide different initial conditions (e.g. starting in-game currency) depending on if it was installed for free or if the user paid to install it. The price will be changing from time to time.
Is it possible for the app to look up this information?
Note: this is not for in-app purchases; I know I can look that up using StoreKit.
It looks like there are hacks and workarounds that get you part way there but for what you're trying to do you need a fully working solution so it looks like you can't which is too bad, I love a good hack :)
Edit: future readers should read the comments for a full discussion.
One idea is to save the current date at the start of the program, to a variable that is nil until it is first set. Then you have the date when the app is first run.
You may also check the date of the Documents folder which is created when the App is downloaded.
If you store this date as a user preference variable then it is preserved event when you update the App.
Then you can compare that date to data you get from your server.
We've got a strange problem that is very hard to troubleshoot. We are looking for some assistance on methods that might help us troubleshoot this problem. We use memcache and thinksphinx. Recently we moved to a new server and suddenly elements on the pages are showing up missing.
So for instance, our home page has news items and latest files added. In one case I see that we are missing the last 2 news items. My developer checks and sees its there. 10 minutes later he checks and see all the news items missing. Check again 15 minutes later and missing 3 items.
We were able to notice that on the server move we had memcache set at 2mb, so we moved it up to 1gb. It looked like everything was fixed. However, now we are seeing similar inconsistencies when people are searching. Users will report problems, I will see them, send them to my developer and he sees different results. We both refresh and see something else.
We are able to realize this is somehow related to memcache and/or our thinkingsphinx, because when we clear and rebuild, everything acts normal.
My only assumption is that at some point we run out of memory in memcache, but it makes no sense that only certain data would not be shown.
Can anyone give any advice?
Thanks,
Will