Recently i have submitted an to app hub, App got Certified and got a mail from microsoft saying congrats app got certified , in app hub A small dialog box in red asked for please update additional details/ update latest package - clicked on it redirected to all the details we have submitted during our app submission -pressed next - next - says successfully app got submitted and now app life cycle status has gone to step 1 again .
1) In my view all submitted apps section , same app shows in submitted and also in published sections.
2)Its Already 24 hours after my app got certified but my app is not in market place.
3)Application lifecycle now shows submission started - checked and submission completed - checked and 2 and 3rd steps (certification and publish ) unchecked.
4)Did i do anything wrong or is it in - track that we have to submit additional details / updated package before publishing it to windows market place.
Please help me out , and i request all of you to provide me the required guidance.
Nothing to worry. I faced a similar situation earlier.
It takes a few days for your app to appear in the Marketplace after successful certification. It is the problem with Microsoft Marketplace.
However, ans to your 4th point, It is not a process to update details. It was actually offering us to submit an update for the app, if any.
Only thing you need to make sure is, whether you have given valid keywords which helps the users find your app in the marketplace.
if you are publishing to multiple market, it will take time for it to appear in all market and could take more than 24hrs. seem like an issue from microsoft.
Related
When I try to publish a release in the Google Play Console, I constantly get this error:
Your app cannot be published yet. Complete the steps listed on the Dashboard.
And yes, I have indeed completed all the steps listed in the dashboard. I am using the new Play Console Beta, this is possibly related. What do I need to do before I can publish a release? Is there a hidden step?
After some searching, I found the button 'Use classic Play Console'. Apparently there are some steps to be finished that are simply not visible in the Beta:
Click on Use classic Play Console
Go to Pricing & distribution
Check the Content guidelines checkmark
Check the US export laws checkmark
Press Save draft
And you're good to go!
I had that problem and fix it. the problem caused by google console because they added one additional task in the app content about wither your app is consider a news app or not. so go to the inbox in your app and you will find that message from google click and you will be leaded to the content that you should fill. I hope that help any one having that issue.
I also had this problem. It was regarding setting your app as free from the App Pricing section as my application was free. So after setting that, I released my app.
I am trying to build a Teams tab using an SPFx web part for a demo.
On my inital app the Sync to teams button in the app catalog was failing with this console error being returned...
https://{TENANT}/sites/AppCatalog/_api/web/tenantappcatalog/SyncSolutionToTeams 400
After running into this problem I started again and this time followed the below tutorial step by step but on my tenant the Sync to Teams button is disabled (This step is near in the end in the Making the web part available in Microsoft Teams section)
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
I then tried to follow the alternative method of side-loading the app by creating a manifest manually using this tutorial...
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/creating-team-manifest-manually-for-webpart
This resuted in the installation succeeding as far as the setup tab screen (this provides a preview of your tab in a model popup before adding the tab to a channel)
The result was "Sorry, something went wrong" (This was the end result of side-loading both my customised web part another freshly yo sharepoint generated scaffold.
Really stuck on whether there's a tenant issue or maybe some node package or SPFx version issue.
Any thoughts would be greatly appreciated.
I received a same error from console which led me to this article.
In this case, the app was already synced to Teams store. If that's the case, you should find and remove it by opening Teams -> Apps -> Built for [tenantname]. After removing it here, I am able to successfully sync my app once more.
I'm using SPFx 1.8.1 version and added TeamsTab in supportedHosts manifest file. Deployed in tenant app catalog and tried to Sync to Teams. Then I'm getting same issue of SyncSolutionToTeams with 400 error. Please find the attached screenshot from console windwow.
The error occurs if the app is still in the Teams catalog. It doesn't override it and instead throws the error. This is a known bug and we will look to fix it in the future. For now, please try either manually updating the app from Teams (not from the SharePoint app catalog) or to delete the Teams app and then to resync from SharePoint.
In my case this error occurs when I changed title in webpart manifest file (webpart.manifest.json). When I rejected the change, it works. Probably there was some inconsistency in project files.
I created an chrome web store entry here:
https://chrome.google.com/webstore/detail/forum/knpdbggaikbgjbgihfgefcjdabkhfgbp
And filled out the form for submission for google app marketplace:
https://docs.google.com/a/nimbusbase.com/forms/d/14QOb8PbSLKDgwIp8Zv-luoAAVurPXUqtzL0Hgikp3rk/viewform
This was over 1.5 month ago. Since then, I have not had any word about my app rejection or seen it in the google app marketplace.
I'm not sure what the process for app review is. Does no word ever back mean your app is rejected?
Typically if you don't hear anything back from us that is a good thing! However, in your case, it appears that you have not set up your manifest file correctly. You have failed to include the DOMAIN_INSTALLABLE container. Take a look at the documentation at:
https://developers.google.com/apps-marketplace
You'll find an example manifest file that you can model yours after.
Since the manifest file was never set up correctly, the application did not enter our review queue which is why you never heard anything about it.
I am trying to update an application from the Google Play Console. The new version of the apk is uploaded as a beta test and I have obtained a link to download the beta test app. However, the link just redirects me to the Google Play where the current version of the app is shown.
Is there something wrong with my operations?? The testing link is obtained in the beta test page tab, from the link in "Beta testers" box. Does anyone know how I can obtain a link to the beta test app rather than the currently published version??? Many Thanks!!
Per:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
You need to be registered as a member of a Google + or Google Group that is designated for Beta or Alpha testing by the Developer. If you are not registered, you will only be able to download the production app from Google Play, NOT the Beta or Alpha version of the app from Google Play.
Having the "link" won't be sufficient, you need to opt-in to the beta or alpha via Google + or Google Group.
Please note that even if you properly opt-in via Google + or Google Groups as defined by the developer, you will need to wait several hours (perhaps 2-8 hours) for your status to propagate via Google Play.
So, perhaps you need to wait 2-8 hours even if your Beta/Alpha status is proper?
Hope this helps!
This is a simple questions:
I've developed my first app for windows phone 7 (Mango). I have created a new release in the marketplace for beta test.
I have received one confirm email about this process. All is ok. But now, in this email, there is a Url like this:
zune://navigate/?appid=46546c45-7b41-11ae-b78e-268334559f0ac
In theory, I have to send this url to beta testing people of my list. But Where I or they have to write this url for download the app?
In zune? In the marketplace? I don't know what I have to do with this url....
Thanks guys,
JPe
When you submitted the app for beta testing, you needed to specify the live ids of some testers. This link (zune://) can be used to install the application through Zune. You need to send this link to those testers whose live ids you entered there. Just paste the link in any browser and it will open with Zune.
The link will not work for anyone else, but for the specified live ids.
If your live id is not in the beta tester live ids list, I am not sure that you can test the app with your live id. I'd suggest to add your live id to the list.
And by the way, you cannot access a beta app through the Marketplace, the only way is through Zune with the given link.
I hope it will work for you.
I have found in most cases the beta links only work when opened from a Windows 7 device, opening the link on a PC through Zune either gets a "app not available" or "app not available for your country".
There doesn't seem to be any setting in the marketplace to get around this so it may be by design.
No word yet on if this is fixed with the web marketplace but I doubt it since the Beta apps only give a Zune link