A submission has been in the certification phase for more than 2 weeks, and it can't be cannelled. The dashboard says a few but could be up to 3 days.
I tried to cancel the submission serveral times, nothing changed. The certification is always at "Pre-processing".
Try running the Windows App Certification Kit (WACK) locally to see if it passes there. https://learn.microsoft.com/en-us/windows/uwp/debug-test-perf/windows-app-certification-kit
If the tests fail locally, you'll have an error report describing what problem(s) occurred.
If WACK tests pass locally, but certification fails/hangs in the dashboard, without showing any error report, you'll likely need support from the dashboard team who can look into the specific package and find out why it's stuck. You can loop them in by going to http://aka.ms/storesupport, selecting contact us, and then choose the Dasbhoard topic, App submissions issue type, and package management subcategory. There's options to chat or submit an incident there. They should be able to tell you why it's failing.
Related
We created an app and uploaded the bundle from dev1 developer account.
The app is in draft stage as can be seen in the screenshot below
We created the internal testing track and send the link to 4 friends to install and provide feedback.
Later we decided we want to publish/release the app from a different developer account (dev2)
We paused the internal track , uninstalled the app and requested google support to delete the app. However support is saying that as the application has 'install statistics' they cannot delete the application at this time.
Question 1: As per https://support.google.com/googleplay/android-developer/answer/9023647 it should be possible to delete a draft. Am I misunderstanding draft status somehow?
Question 2: Is there something I can do to reset the install statistics. I could not find clear meaning of 'App must have 0 lifetime installs'. From literal meaning it appears if any one installs it even once, then it can never be deleted.
Question 3: If it is not possible to delete the app, is following workaround inline with google's policies
We leave the application as is in dev1 account (i.e. not published, internal testing track paused) .
We also unhook this version of the application from the back end server.
There after we publish the app from a different account (dev2) with new package name.
I Submitted my application to the Itunes Connect Service to use TestFlight for internal testing, I have 2 Testers invited that have accepted however nothing is showing up on the test-flight app
And when I go to the testers on test-flights I just see that "No Builds Available"
Am I missing a step? Submit Say no To Encryption Warning , Add Testers.
Review or no Review Same Result
When trying to install our application in the g suite marketplace, users face 404 error after approving the permissions https://www.screencast.com/t/C6tuwym8Sp.
when closing the popup we have another 2 step pop-up which doesn't lead anywhere, not calling the callback url. In the apps section in the g suite admin dashboard we can see that the application was integrated.
This behavior is breaking our flow as users are integrated in the g suite marketplace are out of sync in our backend.
This should be fixed already, let me know if that's not the case.
Looking into building some Gsuite Marketplace apps, but we have having issues at the publish time already.
Publishing an app following these steps makes the app to be accessible from the Chrome Marketplace.
(e.g. https://chrome.google.com/webstore/detail/qwertzuiopasdfghjkl/publish-accepted)
Using Chrome web store app link (e.g. https://chrome.google.com/webstore/detail/app-name/qwertzuiopasdfghjkl)
redirects to a Gsuite link (e.g. https://gsuite.google.com/marketplace/app/qwertzuiopasdfghjkl?pann=cwsdp&hl=en-US) but brings a 404 page.
Waiting seems to do the job (url works after a couple of days - approval)
Changing app type from "Private" to "Unlisted" break it completely; even waiting up to a week, the link never works again.
My questions are:
How do you switch between "Visibility options" without breaking your
app?
How do you guys deal with updating publishing apps on Gsuite
Marketplace and keep it working?
Cheers!
Every new update requires a new installation. So everytime you make changes whether feature or visibility settings, treat it as if you were uploading a new app.
If you change the visibility, it will undergo a review process as if it were a new app.
Users who have already installed your app will still be able to use it.
I had submitted a Teams App for approval. The approval has Failed with primary reason being "We could not install your app"
I would like to know how exactly the app is tested. I had submitted a zip file containing the manifest.json as part of the submission. How is the validation team going about using the zip file and manifest.json? I am able to install the app(bot) without any issues with my test accounts for 1:1 chats. If the validation team can let us know the steps they are following to test the app, then we can try replicating those to see if we get the same error.
The testing procedure in the Microsoft documentation is as mentioned in this link: https://msdn.microsoft.com/en-us/microsoft-teams/botsadd#adding-a-bot-for-11-chat-only
Is the validation team is trying to sideload the app into a team as a result of which they are seeing an error on installation. The app is not meant for use in teams. It is for use in 1:1 chats only. Listing the steps that the validation team is following will be of much help!
All Teams apps must be packaged and sideloaded per instructions on MSDN:
Packaging: https://msdn.microsoft.com/en-us/microsoft-teams/createpackage
Sideloading: https://msdn.microsoft.com/en-us/microsoft-teams/sideload
The 1:1 testing link you refer to is only for that: local testing. For apps submitted to the store, you need to follow the above steps.
In other words, sideload the same app package you want to upload to the store. Does it load?
A couple things to check:
To ensure your manifest is well structured, use the schema Intellisense tip mentioned here: https://msdn.microsoft.com/en-us/microsoft-teams/schema
There is a known issue with description.full length - keep it under 255 characters for now.