After generating APK definition file, i tried to publish it on play console by following below reference
Reference : Publish an externally hosted app in the Play Console
step-1) Sign in to the Play Console with your organization's administrator account.
step-2) Create a private app by publishing to your own organization. Ensure you add at least one organization to Private app access.
step-3) Click Upload external APKs.
Issue : In step-2 we need to create new app in play console. I'm unable to create new app when login play console with enterprise account(Not an Android Developer Account) create app button is noneditable, do i need to add any other settings to make it editable.
You need to have android developer account for creating apps, there is a fees of 25$ to create developer account.
Unfortunately, you cannot use your enterprise account to create apps in the Play Developer Console, you need to have a Google Play Developer Account to do this. However, you can use the following steps to create an externally hosted app:
Upload an apk via iFrame with the same app id as the app you want to host externally. This will essentially act as a “dummy” app.
Generate a JSON metadata file using the steps described here. Make sure that the version of this externally hosted apk is higher than the one uploaded via iFrame.
On the iFrame, click the app and open the Play Developer Console via the “Make advanced edits” button.
Create a new release by navigating through the sidebar, then Production > Create new release.
Upload your JSON metadata file under “App bundles and APK”.
Then, Save > Review Release > Start rollout to production.
Related
I created an SPFX application with the Teams Toolkit that utilises Microsoft Graph API to get data,after packaging and deploying the manifest folder to Teams Admin Center, it renders well with accounts that have Teams Admin and Global Admin access but accounts without this access are unable to access the application as it shows an error as seen in the image.
The Component ID and version in the message are speaking to the React-dom component id and version in the project.
Please i need suggestions on how to resolve this as i am not sure if its just a permission issue
I have tried updating my spfx version but that didnt work as i was already working with the required version of spfx and all other dependency versions
You can raise an issue in https://github.com/OfficeDev/TeamsFx/issues so we can support you better.
I tried to reproduce your issue but failed. The web part displays successfully for account without Teams/Global Admin in my side. Let's clarify the steps before the issue happens:
Create a SPFx project in Teams Toolkit and utilizes Microsoft
Graph API to get data
Click 'Provision in the cloud' to provision
the Teams app (with Teams/Global admin account)
Click 'Deploy to
the cloud' to generate the sppkg and deploy it to SharePoint (with
Teams/Global admin account)
Click 'Publish to Teams' to publish
the Teams app manifest in Teams app catalog (with Teams/Global admin
account)
Approve the submission in Teams admin portal
Install
and open the Teams App in Teams with Teams/Global admin account and
the web part displayed successfully
Install and open the Teams
App in Teams without Teams/Global admin account and the web part
shows error.
Could you help confirm whether you're having the steps above to reproduce the issue?
BTW, after deploying you should be able to use the web part with normal account in regular page in SharePoint. Maybe you can check whether everything is OK in SharePoint app catalog
SPFx solution after deploy to SP app catalog
I have created a Teams App with the App Studio. When I install it with App Studio everything is working? I am now trying to publish the app to the tenant app store
I have downloaded the app packaged from App Studio and uploaded the package to the Teams admin portal. The package uploads without any errors and the app is shown in the catalog list as a custom app
I have enabled
“Allow third party app”,” Allow any new third party apps… ” “Allow interaction with custom apps” on ”org-wide app” settings
-the global Permission policy I have “Allow all apps” on the three subjects
-the Global Setup Policy I have “Upload custom apps” and ”Allow user pinning” on
But my app does not show in the catalogue in the Teams client
After adding and removing the same police, restarting the client multiple times and waiting 48 hours- The app now show up in the catalog
My requirement is to develop an application that should
create static html files
create a new site (with the static html files in #1) in Azure App Service or Hosting server.
i.e for #2,I need to automate the Publish activity that's done from Visual Studio to take it to the public server. So say on a Button click, the app should use the required details like credentials, app service\hosting provider details... and create a new site there.
My Query
Is this possible?
If so please do share it with me or send me some pointers on it.
Else let me know how I can implement this.
You could create azure app service using rest api with this link.
Also, you could deploy webapp to azure app service with ZIP or WAR file. Please refer to this one.
The required details like credentials, app service\hosting provider details you need to manually fill down to achieve deploy webapp function.
Lets say A is the owner. I want B, C and D users from our team to be able to upload the new versions of our application. Is this possible?
From this it is not very clear to me what kind of permission has a user.
If somebody has any experience to this part is welcome.
You need the google account details to sign in to the Developer Console.
Any application uploaded to the play store must be signed.
From Google documentation
Android requires that all apps be digitally signed with a certificate before they can be installed. Android uses this certificate to identify the author of an app, and the certificate does not need to be signed by a certificate authority. Android apps often use self-signed certificates. The app developer holds the certificate's private key.
Signed apk file have a binary file it build and signed with.
Only the developer have this file on his own computer . Once an application first signed and was uploaded to the store all the other versions of the app must build and be signed against the same binary file.
If a developer looses this file he will no longer be able to publish updates to his own app .
Warning: Keep your keystore and private key in a safe and secure place, and ensure that you have secure backups of them. If you publish an app to Google Play and then lose the key with which you signed your app, you will not be able to publish any updates to your app, since you must always sign all versions of your app with the same key.
(from the same link)
It is possible to add another user permission to your Developer console.
Here list of permissions you can choose to share:
Create & edit draft apps
Edit store listing, pricing & distribution
Manage Production APKs
Manage Alpha & Beta APKs
Manage Alpha & Beta users
View financial reports
Reply to reviews
Edit games
Publish games
View AdWords campaigns
Create AdWords campaigns
These permissions can be Global to all apps on account or only for particular apps.
Anyway if you share Manage Production APKs permission you'll have to share the signature file as well.
I am trying to integrate facebook into a Windows Store App.
I have created a new FB App and started working through the steps described in this blog post. http://blogs.windows.com/buildingapps/2013/11/14/facebook-login-for-windows-store-apps/
Here is where I ran into a problem. Step 2 describes how to obtain a Windows SID for an App that has yet to be published. However my app is already published. Does anyone know how to obtain a SID for an app that is already published in the Windows Store?
Instructions in this post should help you find how to locate SID for published app: https://msdn.microsoft.com/en-us/library/windows/apps/hh465407.aspx
It's listed under step 3 for obtaining the credentials for your app. Here are the steps:
Go to the Windows Store apps page of the Windows Dev Center and sign in with your Microsoft account.
Once you have signed in, click the Dashboard link.
On the Dashboard, select Submit an app.
On the Submit an app page, select App name.
Select the Services link.
On the Services page, select the Live Services link found under the Microsoft Azure Mobile Services section.
On the Push notifications and Live Connect services info page, select Identifying your app.
The Identifying your app page gives you an identity element to include in your app's manifest. Open your manifest in a text editor and add that element as the page instructs.
9.Click the Authenticating your service link at the bottom of that same Identifying your app page.
The Authenticating your service page provides your security identifier (SID) and client secret.
I see it's an old post, but I guess it's better to show a simpler solution, which is the one told by microsoft in this thread: https://msdn.microsoft.com/en-us/windows/uwp/publish/view-app-identity-details
You can just go to your application from the developer dashboard, then on the left you should expand the "App Management" option and choose "App Identity". There you can find many informations, including the App SID.