No full-size app banner :Eligibility issues by version - google-play

I am trying to publish an update to my android app and the review done by play console is rejecting the app. I have added different xhdpi icons and changed the app title as well. More than 4-5 iterations have been done.
I have already added xhdpi icons and changed the title of the icons/banners to match the app title. Added icons in the drawable folder
No specific code.
Successful app publishing.
Please refer the message
Following is the message:-

I want to post an update here. The issue got resolved when I added the app title on the image used as a banner/icon.
I received a detailed response from Google Playstore team that my app banner/icon was not having app title which should be visible for end users trying to lauch the app from launcher.
Following was the response.
Please note that our banner requirements are as follows: App name
must be included in the image.

It looks like you are targeting Android TV. Do you want to? If you do, then click on the link in the message you were sent. It will take you to the docs on providing a Home Screen Banner inside your app.
If you think you have done this then update your question to show your AndroidManifest.xml.

Related

Can't publish initial build of app in Google Play Console

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.

Issues showing SPFX webpart in teams tab

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.

Google Apps Marketplace SDK : setup a contextual gadget

Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....

Doesn't WMAppManifest.xml get overwritten?

An update to my WP7 app was just released. When I'm developing locally, I set the Title of the app to be an abbreviation so I know which is which (local dev or published copy) when launching from the app menu.
I forgot to change the abbreviation back to the full name when published, but I thought that everything in the WMAppManifest.xml was overwritten with the metadata you enter in the app hub anyway.
That information you enter while submitting is for the marketplace. The Title to be displayed in the phone is extracted from your .xap. Thus, you may see the correct title in the marketplace but not on the device.
Also happened to me once :).

how to change a Windows phone 7 market place application icon

I uploaded windows phone 7 app in market and it's rejected by apphub market,with reason of displaying default app icon,here the application icon is not being displayed instead it shows an default application icon.I also uploaded all design images in artwork design with suitable dimension of icon.Please help me to show application icon in market place.
Have a look at the end of this post
It shows how to set these icons. (The posts starts with drawing them but you could skip that)
If you are looking in the app hub at the details of your released ap, this always shows the default "cog" app at the top.
If you've uploaded the correcct images these will be seen in the application artwork section of the page.
If the wrong images are being displayed in the marketplace, is this the phone marketplace or the desktop one? Or both?
If the images displayed in the marketplace don't match the ones listed in the details in the app hub then you should contact app hub support.

Resources