After I developped my Firefox OS application, I submitted it on the marketplace. After a few days, my queue position became 10 of xx (and didn't move) :
Created: May 29, 2013
Status: Pending approval
Packaged App Version: 0.6.1
Queue position: 10 of 108
Estimated waiting time: 1 working day
Price: FREE
Since a few weeks, it became 5 of xx and didn't move neither :
Created: May 29, 2013
Status: Pending approval
Packaged App Version: 0.6.1
Queue position: 5 of 108
Estimated waiting time: 1 working day
Price: FREE
So, since a lot of weeks, the estimated waiting time is stopped to "1 working day".
When is my app supposed to be released and is it a known issue ?
The app validation is manual. So the time for validating an app can be long.
Mozilla looks for new reviewers for improving this time (Source : https://blog.mozilla.org/apps/2013/05/20/become-a-marketplace-app-reviewer/)
Related
I have deployed a .Net Core (MVC) Application on IIS server which is throwing 502 error exactly at 10 PM on daily basis, otherwise the application works fine the whole time. I have reviewed my code several time and removed every extra things from the code, but still getting this error at that specific time. Please help.
Have you gone through server logs to understand what is going on at 10 PM? To find logs, search for the Event Viewer. Alternatively, from the Control Panel, choose Administrative Tools and then Event Viewer.
System: Expand Windows Logs; System will be listed underneath.
Filter the log for networking entries
Diagnostics-Networking: Expand Applications and Services Logs, then Microsoft, then Windows.
I have been facing this issue particularly today while deploying my application to the azure environment using Azure Devops.
One of the deployment task fails with the following eror message:
##[debug]Deployment Failed with Error: TypeError: Cannot read property 'scmUri' of undefined
When I retry to deploy a couple of times it succeeds and deployment is successfully done.
What is the issue causing this error?
Microsoft is aware:
We're investigating Intermittent failures of Release Pipelines in West Europe.
Customer using Azure App Service Deploy task in their Release Pipelines might see intermittent errors like: "##[error]TypeError: Cannot read property 'scmUri' of undefined"
Retrying the release may succeed.
Next Update: Before Wednesday, October 17th 2018 15:50 UTC
Source: https://blogs.msdn.microsoft.com/vsoservice/?p=17835.
Hopefully we'll get a response soon.
The latest report from https://blogs.msdn.microsoft.com/vsoservice/?p=17835:
Final Update: Wednesday, October 17th 2018 20:14 UTC
We’ve confirmed that all systems are back to normal as of 2018/10/17 19:35 UTC. Our logs show the incident started on 2018/10/17 13:42 UTC and that during the 5 hours and 53 minutes that it took to resolve the issue. Customers using Azure App Service Deploy task in their Release Pipelines might see intermittent errors like: "##[error]TypeError: Cannot read property 'scmUri' of undefined". Sorry for any inconvenience this may have caused.
Root Cause: Initial diagnosis from the Azure Web Apps team points to
issues with a few of their back end nodes sending bad api responses.
Chance of Re-occurrence: Medium
Lessons Learned: We are working both
minimizing resource-intensive activities in our post-deployment
steps, and are also working targeting monitors specifically to detect
post-deployment issues in the future.
Incident Timeline: 5 hours & 23
minutes – 2018/10/17 13:42 UTC through 2018/10/17 19:35 UTC
Sincerely,
Randy
Trying to manually backup my web app + database using the Azure portal (in the "My Web App" > Backup blade) but I am getting the following error. Any ideas?
Cannot create a sandboxed process, error code: -2147024846
Here's the full log:
Backup Id
123209
Status
Failed
Created Time
tisdag 19 december 2017 19:00:09 CET
Download Backup Zip
Zip contains the backup of an app
Download
Finished Time
tisdag 19 december 2017 19:09:29 CET
Size Of Backup
0MB
Log Details
Cannot create a sandboxed process, error code: -2147024846
Seems fixed now. I suspect subscription payment delay issue.
Also, I’m on a pay as you go sub so I’m not eligible for support.
I am facing a strange issue. I have a UWP app published in store. When I deploy this app to my Lumia 930 through the store, it runs very slowly. However, the same app when I deploy to the same device in debug mode from VS 2015, it works fast. To be specific, I am relying on heaving caching in a Sqlite database for displaying the results, plus I also have lot of List processing done in my logic. In debug mode, one specific page with particular set of data takes around 3 seconds to load and show the results. The same page with same data takes 8-9 seconds when running on the same device but downloaded from the store.
Any idea, what I am doing wrong, or is there something which I am missing. The particular app in question is: https://www.microsoft.com/en-us/store/apps/series-tracker/9nblggh3slj9
Appreciate your help.
This is driving me crazy: We have a Windows Azure cloud service with a ASP.NET MVC 3 project. There have been many changes lately, so we have to deploy it every few days.
Sometimes (e.g. now), we're stuck on the following deployment error:
Role instances recycled for a certain amount of times during an update or upgrade operation...
manage.windowsazure.com tells us that instance 0 of our Staging deployment is non-healthy:
Recycling (Role has encountered an error and has stopped)
Instance 1 however is fine, the web services on instance 1 are working, so the cause of the error is not our code.
We RDP'ed to the instance and examined the Application Event Log, which displays the following error multiple times:
Faulting application name: WaHostBootstrapper.exe, version: 6.0.6002.18488, time stamp: 0x505cf7da
Faulting module name: ntdll.dll, version: 6.1.7601.17696, time stamp: 0x4e8147f0
Exception code: 0xc0000008
Fault offset: 0x00000000000d4995
Faulting process id: 0x970
Faulting application start time: 0x01ce474976d706d2
Faulting application path: E:\base\x64\WaHostBootstrapper.exe
Faulting module path: D:\Windows\SYSTEM32\ntdll.dll
Report Id: c26d8be8-b33c-11e2-a9be-00155d3ab8c9
When this happens, we are
Re-imaging the instance
Re-booting the instance
Deploying again
Creating a support ticket
Some hours later, everything works again. We didn't change anything in the deployment, it just works again, like it did before. At the time Microsoft Support is reacting, everything is fine again, so we cannot show them the problem.
This is so ridiculous and frustrating. We're losing days of work just because of this silly error.
Anyone else having these problems? Any ideas how we could stop that?
Check following:
1. You have latest Azure SDK and your solution is using the correct dll references. e.g. Make sure that if you have v2.0, all references use same version. If not, build afresh.
2. All references (including packages and own libraries) are enabled with "Copy Local" = True and they are included in the package bin.
3. If you are using Storage, check the connection strings and validity of keys.
4. Check whether service configuration has correct osFamily and osVersion that you are targeting.
5. If nothing helps, try intelliTrace.
for such kind of issues we found http://blogs.msdn.com/b/kwill/archive/2013/10/03/troubleshooting-scenario-7-role-recycling.aspx to be a good resource for debugging.