In Google Play Console, I created a new app and uploaded an application bundle for internal testing.
Play Console set my app's application name to the applicationId field of my build.gradle file, which is not the application name I want it to have (lets say com.wrongName.app).
I want to change the application name, but if I upload a new application bundle, I get:
Your APK or Android App Bundle needs to have the package name com.wrongName.app
This thread seems to imply that I can still delete the app bundle and load a new one, since this is still a draft. But I see no way to delete an app bundle, or even delete my app.
Am I stuck with the wrong application name?
Yes you can delete the app bundle, and delete the app as well. There is a provision in the Play Console for that. The Package name has to be identical to your App Name as well, without which you will not be able to upload it.
Related
I have succedeed in deploying a simple client web part on a SharePoint 2016 site with the following steps (following many guides, including https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2016/):
I configured the required Service applications (subscription and app management) and managed the blocked file types.
I created an App Catalog site for my Web Application.
I wrote two urls in "Central Administration -> Apps -> Configure App URLs" (it seems that it doesn't matter what URLs I write, the important thing is that they are not empty or I can't add the App to my sites).
I set up my CDN by creating a Document Library and a folder. I specified this location in the write-manifest.json -> "cdnBasePath".
I uploaded the sppkg (output of gulp package-solution --ship) to the App Catalog and it got distributed succesfully.
I went to the root web of the site collection I was working on and added the App.
I created a web part page with an empty web part zone and.
I succesfully added the client web part that was in the default "Other" group, and it rendered fine in the page.
Until here everything is fine. There was some tweaking to do with yeoman, gulp and node versions, but it works.
The problem is that if I add the app to the site root web, the web part is not available to the other webs, since from what I read, if I add an app that way the scope is only that web. In order to make the web part available on other webs, I would have to go to every web and add the app there. This could be fine if I had 2 or 3 webs, but what if I have 1000 webs?
I also read that if you add the app to the App Catalog Site, the scope should be "tenant", and you can then choose where to distribute the app so that it's added for all webs from this page:
https://i.stack.imgur.com/MAX8K.png
If I add the target site here, and the press "OK", an exception occurs:
Exception in page: https://i.stack.imgur.com/S8cl1.png
Exception in log: https://i.stack.imgur.com/K2GMB.png
I tried debuggingg the Microsoft.SharePoint.ApplicationPages.AppInvPage.SetControlStateUsingAppInstanceId method with dotpeek and I think I was able to identify the problem with the AppManifest object, that seems to have some null fields that on which gets called a "ToString", but wasn't able to pinpoint the exact problem yet.
So I thought I could maybe write some PowerShell script to add the App to all subsites, but it seems the method require some parameters that somehow don't seem right. For example, Install-SPApp requires a SPApp object that is obtained with Import-SPAppPackage. Even if I manage to launch the command with the .sppkg file stream, when you launch Install-SPApp an exception occurs: "Install-SPApp : Value cannot be null.".
Honestly I'm running out of ideas.
TL;DR: Has anyone had issues with SharePoint 2016 and globally deployed client web parts? Is it possible to automatically add the app containing one or more client web parts to all subsite on SharePoint 2016?
I'm working with the new Azure Static Web Apps Preview product, not to be confused with Azure Web Apps.
My Angular 9 app, which runs fine locally, is all set up for internationalization, and one effect of the internationalization is that it drops my index.html into app/catfood/dist/en_US rather than app/catfood/dist.
This is leaving me stuck in terms of how to set the app_artifact_location value in the workflow file. If I leave it at the default value of "dist/catfood" the build gives me this error, which honestly does seem accurate as the index.html isn't going to be there:
Failed to find a default file in the app artifacts folder (dist/congruence-web). Valid default files: index.html,Index.html.
If your application contains purely static content, please verify that the variable 'app_location' in your workflow file (located in .github/workflows) points to the root of your application.
If your application requires build steps, please validate that a default file exists in the build output directory.
But if I change it to the logical "dist/catfood/en_US" I get this error:
The app build failed to produce artifact folder: 'dist/catfood/en_US'. Please ensure this property is configured correctly in your workflow file.
Really not sure what the build system is expecting of me. What should I be using for app_artifact_location? Or am I even tweaking the wrong thing here?
Update: When I deliberately turn off i18n in angular.json, the en_US directory goes away and index.html is found in dist/catfood and everything works great. So basically the problem is "Why does Azure Static Web Apps not understand localized Angular applications?"
I am developing a chatbot azure service, which I want to integrate within Microsoft Teams. So far everything is working but the "re-install" of the package in the Microsoft Teams.
I created a publish "folder-profile". Then I zip the result with the manifest.json and the icon files inside. I go to the Manage Team section and in the Apps tab I select upload a custom app. Then I choose the .zip file and the service seems to be there(Actually it is there)
It works, but when I create a new version and I repeat the described steps, it seems like Microsoft Teams is still using my old code.
I test the chatbot in the Chat by using #"APP-ID" and I see how my changes work, but installed as an App for the "Team" keeps the old version.
I tried to uninstall it, check if the bot is gone(it is gone) and then upload again, but some kind of cache is there and the bot behaves like in the previous version.
Any idea how is the correct way to deploy new versions of my app in Microsoft Teams?
I think you need to upgrade the version number in the manifest.json file (you can do it in the manifest.source.json before to generate your zip).
A great new plugin was just added to pg.build called LaunchMyApp which allows an app to be launched from an url.
The problem with this is that when I open my app from the browser, it creates an instance of the app "inside" the browser. If I then send the app to the background and open it normally from the launcher, this creates two instances of my app.
I guess some would want this behaviour, but to the users of my app I think it will be confusing - so I decided to write a plug-in for running the app as a single instance.
The plug-in itself is extremely simple since it is only supposed to add the attribute
android:launchMode="singleTask"
to the application tag in the androidmanifest.
I can see how I can add new nodes, but not how to add attributes to existing ones.
Is this supported in plugin.xml?
I created an app for imaging application to start with.
Now I had to build another app which uses a lot of functionalities of the previous app.
I copied and pasted the first project, and changed the app Display Name, etc. in WMAppManifest.xml file.
But now when I try to deploy this app, I notice that the first app is replaced by this second one.
How can I resolve this? I suppose I require a different product/publisher ID for this app in Packing section. How do I obtain these?
You don't need to "obtain" these IDs. When you submit your app to the marketplace, they are automatically replaced by the appropriate values. When developing on your computer, just put whatever value you want. The values are located in the application manifest (WMAppManifest.xml).
You can create a GUID in Visual Studio by going in the "Tools" menu, then clicking on "Create GUID".
You need to change the product ID (it's a GUID you can generate a new one).