My Google Action was approved by Reviewer team and it showing deployed on Action console. but users not able to use it and only I can use it in my mobile and that is also test version. What does deployed mean? Will it take some time to reflect?
Once deployed, it does take some time to roll out to all Google servers to be available to everyone. During this time you'll still get it reported as tests.
It should be available to everyone within a few hours.
Related
Usually my target url is alway myprojectid.appspot.com but just about some minutes ago I needed to push an update but i'm getting another target url of myprojectid.uc.r.appspot.com
Please see the image below because I had to abort the process.
How do i fix this?
This is an expected behaviour, as seen here. You can also see the changes made in the releases notes for Google App Engine where it explains that App Engine is now changing the URLs that you use to send requests to your apps.
As stated in the release notes:
For example, an app can receive requests at https://PROJECT_ID.REGION_ID.r.appspot.com. This new URL is optional for existing apps, and will soon be required for all new apps.
If you are trying to deploy a new Google App Engine application, the URL will be the one you are seeing here https://PROJECT_ID.REGION_ID.r.appspot.com.
I hope it helps.
after a little bit of advice. Kind of got myself into a bit of a chicken and egg situation.
So they story is, We have recently completed a major update on some mobile apps (Both iOS and Android). These mobile apps connect to a Azure hosted app service which has also had a number of significant changes including many db structure changes. All of which is currently live in production, so I have to release the updated app service and mobile apps at the same time.
This is where the problem comes in. To make the apps avaliable for review with the relevent stores, I will of course mean I need to have updated the app service so that the updated apps work, but I can't update that until I can release the apps to the general user base.
Any advice on how to get the updated apps approved without breaking things for the current users?
You could use Azure web app deployment slot to set up staging environments.
Deploying your application to a non-production slot has the following benefits:
1.You can validate app changes in a staging deployment slot before swapping it with the production slot.
2.Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your app. The traffic redirection is seamless, and no requests are dropped because of swap operations. You can automate this entire workflow by configuring auto swap when pre-swap validation isn't needed.
3.After a swap, the slot with previously staged app now has the previous production app. If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back.
When you have updated the app service so that the updated apps work, click swap and it will immediately swap to production without breaking things for the current users.
For more details, you could refer to this article to set up staging environments.
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.
We have developed a private WP8 application, and we have registered company account on Windows Phone Dev Center.
The next step is the development of "Company Hub app" which will take care for installation and available updates.
Since we have only one application, I think there is no need to develop "Company Hub app".
Is it possible that the application itself check for any available updates? (We plan to develop webservice for upgrades distribution).
Can I do the following:
Application Check for updates
If so, take the installation of a new version
The application installs a new version of itself. (If this is possible, how to do it?)
So far I have managed to find only examples with "Company Hub app"
Thanks
Selvir K
So far I have managed to find only examples with "Company Hub app"
That's because it's the only way.
To deploy applications on Windows Phone, you have three options:
Using the marketplace
Using the company hub: you get the benefits of the marketplace, but inside of your company network
Using the XAP deploy tool. The phone needs to be developer unlocked (it's a free operation now), there is a limit to the number of apps you can deploy this way on a phone, and you lose the benefits of automatic updates
One alternative way could be to publish an app on the marketplace and mark it as hidden. Only people who have the direct link to your app will be able to download it. Still, if the link to the app is somehow leaked outside of the company, you'll have no way to control who installs the app. So don't do that for critical/confidential applications.
I am in the exact same boat. We are working on our fist wp8 app and do not want a company hub.
I found if you use InstallationManager.AddPackageAsync(String, Uri) method within your app this will go to our website and download\install the xap file very easily. Of course once executed it appears to close your app so it can reinstall but for now this works fine for us.
I happened to see this post as I just finished developing a Windows Phone 8 app for a client, which was in a similar situation. I found publishing to Windows Phone Beta Store severed them the best for the moment for the main reasons below.
The distribution is totally in client's control. The apps in beta
store do not appear nor can be searched in public store. Client just need to send
emails with the app link to its employees. Only the people with the
Windows Accounts added into the tester's list are allowed to download
and install it. Up to 10,000 testers are allowed which is more than
enough for most of the business.
It is much easier to publish it in beta store compared to it is in the
public one. It does not require strict certification as it does in public store. It is an automatic process and only takes a few hours compared to up to two weeks in public store.
From the end users point of view, after it is installed there is no difference. It is the same app and it does not expire (as of today).
Can we get the crsah logs thro app ?
Will NSFileManager/NSData help us to accesss .crash files from iphone ?
Is there any way to get it, except the well-known iTunes sync method...??
Thanks in advance.
Gopi.
There are also other ways: my company just released a service for just that purpose: http://apphance.com . You add a simple framework project to your app, integrate it (takes about 5 minutes) and you can see all the logs and crashes from your application in a web panel, where the logs, crashes, memory exceptions etc. are all available. It's automagically available from a web panel, without telling the tester whet should be sent where. The tester can also report issues directly from the application including screenshots.
The service is currently in closed beta stage and you can request beta access to it.
No, apps can not access their crash logs programatically. Apps can't access the file system outside of their sandbox (i.e. your application's directory).
Yes. Thanks Shaggy Frog.
To get the crash reports , I thought that I need to communicate with an user, and help them find the logs, they can email to me.
But later( after posting this question) I found that, we can get logs from iTunes Connect.
Apple allows us to see the some crash logs ,where developers can manage applications they have on the App Store, check their sales, and get promotional codes for their apps.
http://www.tuaw.com/2009/05/02/itunes-connect-now-lets-developers-see-crash-reports/
Thank you all!!
Have a great day!!