I used to test my Chrome Apps by following these instructions:
https://developers.google.com/chrome/web-store/docs/publish
Now, when I upload a new app for testing, the Publish to Test Accounts button is gone, and it seems to be replaced by a set of radio buttons, one of which is "Trusted Testers", and a single Publish button. When I publish that way, the app gets into a Pending Review state, and stays there (for over a day). It seems as though I've requested it be published for real, which I guess requires a review, but I only want to test it.
A month or so ago when I did this is became available for testing in minutes.
Has anyone successfully this week published an app for testing only?
UPDATE: To get along with my development, I took an app Published to Testers a few weeks ago, and updated it with a completely unrelated app that I'm working on now. It appeared as Published to Testers within a few minutes. So, I am able to reuse this "container" for testing various apps. But, I am unable to publish anything new to testers.
This turned out to be temporary. A day later, publishing became responsibe again, with a quick response.
Related
After a tiring 3.5 months I learned how to build and launch an app using Flutter and Android Studio. I tested in debug mode on various emulators and all worked well.
I then built the app bundle and uploaded on to Google Play Store as an internal release - again everything ran well.
I pushed this in to Production. After a week of waiting for a review, the app launched. I uninstalled the test version and installed the live production version - and that's when the problems started. The app began to crash in places it hadn't before. Namely on certain pages (and often after the render of certain pages the app closes after c.3 seconds) or upon button presses on certain pages.
I have now added Crashlytics to the app (which I didn't have before), and have pushed this as a second version on to the Google Play Store - and again it's pending review. The questions I have are:
Can I deactivate an app once it's live on the app store to prevent any more downloads? - Is there any code that can be added to the app to do this internally? I can not see any options or instructions within the Play Store. It seems a little crazy that I now know my app has 'bugs' which never materalised in test, but i can't 'switch it off'?
I have only been able to add Crashlytics this time for a new production release, and once installed and I can try and work out what the problem is with error logs. Once I have I will have to create a third version and again add as a new release and wait for Google to approve - is this really the most efficient way?
Why would or could a Production release of an app crash when the Debug version, or Production release version in Internal Test mode, did not? - I find it so strange that I have so many tools available and yet none detected a problem until launch
Thanks in advance!
you can unpublish your app from playstore
goto console>select your app>setup>advanced setting>unpublish app
this will stop your app from appearing to new users and getting new download from
playstore
2.fixing bugs always need a new release to update your app there is no way to get around
uploading a new release and waiting for the review to end (this is for production app)
3.your testing might not have encountered any bugs because you might be testing on one
device or emulator with a specific api for example api 30 ,and the bugs are being
detected on other apis or device properties you haven't covered in your testing
I'm working on a group project and we are trying to upload our flutter app to the Google Play Console. The other day, I finished all the processes for submitting the app and now we are waiting for the app approved. However, the app we submitted as the app bundle before doesn't have much functionality. But, one of our MVP was uploading to Google Play, so we just submitted the app having a simple frontend with no functionality to the "internal test", because I thought our app doesn't have enough functionality to release as a closed or open test.
My first question is if it says "pending publication", does it mean they are in the reviewing process and I should just wait for a few days? Another question is is it ok to update our app bundle while they are reviewing our app (since the current app bundle doesn't have much functionality)? And when is the better time to update app bundle next and and how to update? Is it just hit remove in the picture below and drop a new file??
"Pending publication" indeed means that your app is under review. These days, it can take as much as a week to have it reviewed.
You can indeed choose to create another release even while the first one is under review and upload a new App Bundle. In this case, the first release will be aborted in favour of the new one (assuming the two releases are in the same track). As someone pointed out, it is possible that it resets the waiting time for the review.
Regarding your screenshot, the fact that you can see a "Remove" button means that you probably already have created a new release (since existing published release are immutable). Maybe you created a new release in a different track?
Clicking "Remove" and uploading another version of the App Bundle should do it.
I have a beta application that I want to show to 100+ people and I can't figure out how I can do it without the app store. The thing is with the app store it's a beta. In the app it has pages that do nothing because I want to show the people what I'm working on next.
What adds to the problem is that the application is Push notification enabled.
I'm guessing if I sent the files of the code that the certificates would change because they would have to make a new provisioning cert.
http://testflightapp.com is a great tool for distributing beta tests. As for the 100+, it will only support 100 a year as per Apple's ad-hoc constraint, up to 200 devices. To test with more people, you'll need to sign the app again with another developer account and distribute to a second list. Other options include enterprise deployment or having some testers build and deploy for themselves, signing with their own developer account.
I have been looking around for an answer for a specific question but just got hints for it here and there. I want to know when i submit an app for review for the AppStore:
First, how long does the review process usually take? I know that it may vary but just want to have rough estimate if possible
Second, when an app is accepted does it go automatically to the app store or the developer has the control over when to release it there?
Cheers
AF
check out details, which is my recent app on appstore,
It take 1 week for approval , As I remember, it was taken 3 days too once.
Time taken to publish is all in their hand.
App will be publish directly to appstore.
But you can remember the option for publish by you or apple :) at the time of submitting app
From my experience review takes about 2 weeks recently, but it varied from 2 days to about a month in the past.
When you submit an application you have an option - whether to make application available on appstore immediately after it was approved by Apple, or hold it before developer does that manually, so if you did not select that option then Application should be published on Appstore by default. (See pages 75-76 in iTunesConnect Guide (warning - large pdf file here))
I was hoping someone can answer a simple question for me...
If you create an iphone app and get it approved for sale, what happens if you add updates to it? Do you have to submit this for approval too?
How does the whole process of updating existing apps work?
Assistance would be very much appreciated, thanks
Yes, every update requires a new round of approval. Once your first app is live, the management page for your app offers an "Add Version" button, which takes you through a similar process to the original app, but with options to document changes.
You do indeed need to have updates approved. So once your initial application is created in iTunes Connect, uploaded and approved by apple and available through the store, you can easily submit new versions.
You log into iTunes Connect and click Manage my Applications.
Select the application and click the Add Version button.
Fill out details of the update (such as the new version number, what's changed, any new screenshots, etc).
Upload your new binary via the application loader.
Wait for review.
The process of update is almost exactly like the process of creating and pushing out the first release. It's really quite simple, tbh.
The update process is nearly identical to the original submission, except that you don't have to reenter all the metadata (but you can modify almost all of it, except for the app ID, during update submission).
Update review times have historically varied by large amounts, either slower or faster than the original app's approval time, on the order of 1 day to 1 month. Don't count on it being any less.