I am using Play console internal testing with fastlane upload.
Suddenly, Google started review my internal testing.
I know the internal testing is fast distribution process without review for small internal tester group.
Is there any change in policy? I can't understand this issue
I could get a response from google play console help support team.
In my case, my last release was rejected because of invalid test id/password.
So second case includes my case.
Hi there,
I'm sorry we got disconnected during our chat today - please let us know how we can help resolve your issue. If you'd prefer to contact us again via chat support, we're available Monday through Friday, 12 am to 12 am GMT.
We also offer email support 24/7. Just respond to this email and I (or one of my teammates) can pick up where we left off.
In most cases, if you upload an app bundle to an internal test track, changes will be immediately available. App updates on internal test tracks are not subject to reviews but may be subject to retroactive reviews after going live on the Play store.
There are two caveats to note regarding reviews and internal test tracks:
If your app's first release roll-out is on an internal test track, the submission must be reviewed before it can be published. Reviews can take a few hours or up to 7 days (or longer in exceptional cases), as it depends on the review time that your app is subject to.
If your previous submission has been rejected, the next submission must be reviewed before it can be published. In this case, if you upload an app bundle to an internal test track, changes will not become available until the review is complete and approved.
Regards,
Belle
Google Play Developer Support
Related
If I publish v10 of my app into Internal Test Track, and then a day later publish v11 of my app into Production, will the people in my Internal Test Track get the update? Or are they stuck on whatever is the latest version in Internal Test?
User will always receive the highest version available to them. See here under "Version code requirements". So if version on Internal Test track is lower than on Production, they will get production.
recently my company started using Bitrix24 as an intranet portal. Our employees use google drive and calendar synchronization between their google accounts (private ones, not gsuite). Few days ago I received an email from google:
We have contacted Bitrix24 support, but they could not give us any specifics with regards to this email and pointed out to contact google. Free google plans do not really have helpdesk support and point to sites like stackoverflow for help.
We do not really know what to do in this situation, as we have very little knowledge about google developer console. One of us just used his account to set up a project and provide OAuth to sync google accounts with bitrix24.
Several months ago google started releasing security changes enacted to help ensure that users data is secure. Due to this all developers with applications running risky scopes must apply for application verification
The developer who has created this application, probably the same person who received that email must click the link and submit the application. Once your project is approved you will not have any more issues. I suggest you begin the process now as it may take sometime for you to compete the process.
google play developer console has a near channel called "internal test". it is the last one in the list and i took a image of it below. how does it compare with alpha channel ? im not understanding its usecase ? seems your allowed 100 users.
I tried looking for documentation but i only see that it makes the app available faster. is that the prime benefit ?
That is correct, the Internal test track primary advantage is that APKs published to this track are available to testers within seconds, instead of up to several hours for Alpha or Beta.
Also, Internal testers can access app versions that are not otherwise available to other tracks users due to various restrictions such as device exclusions.
Finally, Internal testers do not have to pay to acquire the test version of the app, if the app is paid.
The internal test track is designed for internal testing use cases.
I have an application for various platforms. Let them be iOS, Android and Windows. In order to use a app, a monthly fee needs to be paid, but it just needs to be paid once in order to use all platforms. It is the same as with Spotify, so by paying once, every platform can be used.
According to the guidelines of Google and Apple, I need to offer In-App Purchases for the monthly fee. The system is connected to user accounts, which are managed by a server, which is in my control. I am storing the subscription data of users, so if a user uses the In-App Purchases on iOS, the information is transmitted to the central server in order to unlock the Android-App as well (in case it has been paid on another platform already)
The problem is the following scenario:
A user has a valid subscription which has been payed via Google Play. The iOS and Windows apps are unlocked as well. Now the user uninstalls the Android app, goes to the Google Play website and cancels the subscription. In the current scenario, I am not able to detect this and the subscription will be valid for all other platforms.
The question is:
Is there any pattern to circumvent this problem? Spotify and co are solving this issue as well, so there must be a solution for this
Well, the server that handles the authorization of the user (that is, your server) should query the Google Subscription API, to check if the current subscription is still valid. Each SubscriptionPurchase Resource contains information about when the subscription expires.
(see https://developers.google.com/android-publisher/api-ref/purchases/subscriptions)
For Apple, the same stuff applies: You will get a receipt, and with that receipt, you can query the server at any time to check if that subscription is still valid.
There is a slide which summarizes these points and the pitfalls very well: https://speakerdeck.com/rosapolis/the-recurring-nightmare-cross-platform-in-app-subscription-purchases
Bottom line: You won't be able to make that happen without a server that does the communication between the two stores. It comes with issues, though, as the slide shows.
Bonus: The talk from which the slides are taken is also on Youtube
Open browser
Navigate to http://www.windowsazure.com/en-us/
Select portal top right
login with my email address
Receive the below error
https://manage.windowsazure.com/Error/Login?getsupport=true&f=255&MSPPError=-2147217320
Receive the error
" We are having trouble logging you into the portal
Please contact Customer Service for assistance."
Using IE or Chrome, incognito or not, cookies cleared or not, cache cleared or not. The problem still exists. Also tried on multiple devices media centre PC, desktop running windows 7, iPhone 5, ipad 3...
Prior to November 2012 I have accessed the windows azure subscription without a problem.
I clicked the customer service link and the australian number is 13 20 58 I have contacted that number explaining that I cannot access my windows azure subscription and each time I login I receive an error. They proceed to redirect me to other support teams where I repeat my details and the problem they either redirect me again or provide a number to call.
In one case I was redirected to a number that no longer exists. Another I was told to raise a case on the windows azure portal page the same portal page that I receive an error on when logging in, when I asked for alternative options there were none.
So far I've spoke with the msdn support team, windows subscription support, online services, etc and still no resolution. In the latest call to support they have said to raise the issue on the forums so here goes.
Anyways long story short I have probably spent 3+ hours calling Microsoft support explaining the problem, waiting on hold, being redirect, repeating... still I can't access my windows azure subscription
I checked in commerce.microsoft.com and there is a windows azure subscription associated with my email address
Subscription-1
Windows Azure MSDN - Visual Studio Premium
Does anyone have any suggestions on how to resolve this issue?
Some time it's happened wait for while and retry
or just ask azure support in twitter
Editing for those who are like me and skipped reading the comments (in small font) below the OP's question. This was resolved and was due to the first reason I list below. However, it could (and has) happen in past for other reasons as well, so might as well keep this response here in case it helps someone else out.
Try logging at https://portal.azure.com/
The manage.windowsazure.com isn't even DNS resolvable to any website - I am not sure how you are getting that address (maybe its from some part of Azure IAM pipeline that hasn't been updated) and (more interestingly) how you are able to open that link - Maybe this is something available only in your region ! (but I am stretching here).
Regardless, I also tried to find other instances of similar issues and in general I see this issue is related to cases when the an account has been transitioned to Office 365.
Here an account was moved and resulted in creation of two accounts with different passwords - solution here was to set the Office 365 account (new account) as a co-admin on the old account that was used to setup the Azure account.
Here the account was not provisioned correctly in Azure AD Store and had to be removed and re-created using DirSync
Here, the problem seems to be related to (the new) Account Provisioning in Azure AD.
In general, it seems this is a problem that might be harder to explain to level 1 support. You might have better mileage speaking to your organizations IT admin and have them check for any inconsistencies that might be similar to those stated above.
Try forcing the directory in the URL like so
https://portal.azure.com/#domain.name
For example in case of MS AAD domain
https://portal.azure.com/#mycompany.onmicrosoft.com
In case of custom domain
https://portal.azure.com/#mycompany.com
Sometimes there is some odd behaviour with redirect loops or when you no longer have access to the tenant but you have selected 'last visited' in the Startup directory.
Glad to hear this was resolved by support. Since this was posted, we made a number of updates to the login process and types of accounts (incl. the addition of MFA). At TechEd we announced a new portal (video # http://channel9.msdn.com/Blogs/Windows-Azure/Azure-Preview-portal) if you want to see what is coming.