i created playstore developer console with a help of my friend who lives in Australia.Payment was done from his card now i need to verify my developers account from nepal and it is not verifying from his passport.
Related
I am trying to publish the Azure APIM developer portal - it is enabled for user/pass - authentication. We haven't customized it and are just trying to get it to work.
When I click publish and go to view the portal in a different browser I get the following message
"This is a home page of the Developer portal - an automatically generated, fully customizable website for publishing your API documentation where consumers can discover APIs, learn how to use them, request access, and try them out.
The content hasn't been published yet. You can do so in "Developer portal" section of your API Management Service in the Azure portal. Learn more."
When I go back to the Portal publish page, it resets to show "Publish" as if nothing has happened?
Are there any logs or anything I can test to get this to work?
BTW - the Legacy portal works 100%.
Thank you.
I have Created the APIM instance and added the HTTP Trigger API from Function App and published the developer portal by enabling the CORS option also.
Next, I have created the user and given all APIs Level access in the APIM Instance and opened both deprecated and legacy portal in different browser, logged in with the non-administrative user:
You can see logs of all activities in the Activity log of APIM Instance:
To see the Function App API imported in the APIM Instance, you have to add that API to the products subscribed by that user:
Published the developer portal again with new changes:
Activity Logs:
Result:
You can check each log activity from the Activity log to see complete details whether the operation publish or other is succeeded and how much time it took to complete.
I'm having trouble making my publicly available app script visible to the Domain Admins for domain-wide installation.
G Suite Marketplace SDK is enabled, with the [Configuration] tab configured. The [Publish] tab never seems to enable the [Publish] button, with the warning "This form is only for specific add-ons".
My app has recently been reviewed and allowed to proceed by the review team, and I can see in the Chrome Web Store that my app has been published
Published Version 14 Published
Draft Version 15 - Public Pending Review
GAM: Published
The perma link is available to install the app individually:
https://chrome.google.com/webstore/detail/seal-atn/mojoekeedapimnnamfjgmnoihijnming?utm_source=permalink
However it's not available in the G Suite Marketplace. I can only locate the application when searching for it within a Google Doc. The application doesn't appear to be visible to the Domain Admin user, so they are unable to push the application down onto their end-users
I've read somewhere that there needs to 2 listings in the Chrome Web Store Developer Dashboard, one for the G Suite Marketplace and one for the Chrome Web Store. I've followed the instructions for for publishing domain-wide installation: https://developers.google.com/gsuite/add-ons/how-tos/publish-for-domains
I now have two entries in my chrome dashboard, the new entry is in the following state:
Published
GAM: Pending
Yet the Domain Admins still cannot see the app, even though it's publicly available.
I'm very confused
My details are:
"api_console_project_id": "820114923602"
googleapps_sdk?project=project-id-5892627631604572744
I want to upload my desktop app to windows store.After some searching,I found that first I'll have to test the app with windows certification kit, then create an account on hardware/desktop portal.Submit certification test results to the portal then upload the app using developer account.
Now, for creating a company account in Hardware/Desktop portal, it is asking me to buy a certificate(Class 3 or EV).EV is for LSA and UEFI. And for other services,Class 3 certificate will do.I have no idea what LSA and UEFI are,I just want to upload my app to windows desktop store.
So,which certificate should I buy class 3 or EV.
Any code signing certificate will work well untill you'll need to sign drivers. You can get Comodo Code Signing certificate as cheap or certificate from Verisign if you want to sign drivers too.
As the title says, I would like to deploy my application on multiple phones, without developer unlocking them.
The said application is private, thus it can't be distributed through the store. I've heard of Company app distribution, however it's not clear for me whether it requires a developer unlocked phone or not.
Can you tell me how can I get custom apps on WP8.1 phones, without dev unlock?
The link you have shared describes steps to distribute app internally.
For deployment of company apps developer unlocked phone is not required. Once company app is ready for deployment, you need to install .aetx file which is generated form the code signing certificate. .aetx file can be shared to users through mail which can be accessed through phone to install. Once this is installed you can deploy xap by just clicking on the shared xap file. sharing can be through mail, dropbox, or any secure website.
Let me know if more doubt.
One of our customers likes to test our application while still in Beta and before we are able to deliver the finished app to the store.
Is this possible? The only way I can think of is to unlock a customer device from our developer account. But as you can only register up to 3 devices this is not an option.
Can the customer set up (if willing to) a developer account on his own, register the device as developer device and then install our application. Has someone already done this? Or are the app locked to the developer account which has build the app?
Or can the customer install the windows phone SDK and at least deploy the app to the emulator to have a look at the app?
Regards
You should take advantage of the Beta testing functionality:
Go to the Windows Phone dev center and on the App info page, under More Options, click Beta.
Associate your customers Microsoft accounts (using Live ID)
Upload the XAP
It will generate a link that will allow your customers to test the app.
Only users added in step 2 will be able to download the app.
You can submit a beta app to the store. When submitting the app, you have to specify the live ids of the users participating the beta. Only those users will be able to download the app, and they don't need to have an unlocked device.
Also, to answer your other questions, yes the customer can deploy your XAP in the emulator if he installs the emulator, and no the XAP isn't locked to the developer account which has built the app.