I'm trying to upload a new android apk in the google play console. It has a couple of additional permissions like READ_SMS which is triggering a permissions form that I have filled too. I am however unable to save the data. Error code in logs: 858285013
Error snapshot
I had the same issue in one of my apps. I followed the below steps to resolve the issue.
Upload the new apk with only required permissions in the track which you want
Now you can see the Old apk with retain option
If you click on retain button, you will see permission declaration form
Select No, this release does not meet the SMS and Call Log permission policy option and click on save in bottom right of the page
Now click on discard button
Now create new release and upload the latest APK and fill the declaration form
Save the new changes and now you will able to save the changes
Before that if your app is using RECEIVE_SMS & SEND_SMS to verify the mobile number, then you need to change the implementation of mobile verification. For that you need to use Google's SMS retriver API. If your app comply with the Google developer policy, then you can keep the READ_SMS permission and for that you need to mention the valid reason in the permission declaration form in play console. Or you can remove the READ_SMS permission, and proceed with the flow as mentioned above.
You must Use SMS intent or you need to send a declaration Form... SMS, CALL LOG.. not allowed from 2019 Jan 9th.. Plesse Check this link android SMS Permissions
SMS Permission Declaration Form
Related
Teams Application with a bot and the permission of the file uploading enabled.
Can't see the preview of the attachment sent to this bot on Microsoft Teams even if the JSON response of the file upload confirms the upload success.
The attachment is visible on the browser via the browser link (if we are logged in with the team's web app).
The error message is:
This item might not exist or is no longer available This item might
have been deleted, expired or you might not have permission to view
it. Contact the owner of this item for more information.
This issue got fixed though in this bug
When I change the policy name firstpolicy to secondpolicy on the device, the patch API response is 200 ok and it removes apps of first policy to apps of second policy from the play store app, but it did not remove them from the device. It still shows apps of the first policy.
I am using an update mask.
Testing fully managed device
Any help appreciated.
The stack overflow thread at Android Device Policy sync does not work until done manually mentions a reboot will force apply a policy, which isn't ideal but it does at least ensure a policy is updated. I'm also testing a fully managed device.
https://developers.google.com/android/management/reference/rest/v1/enterprises.devices/issueCommand details the standard for sending a command to a device. You can test it against live data with the API explorer on that page, so navigate towards the bottom of the page where it says 'Request Parameters' -> 'Name', and put in your enterprise & device ids of the form 'enterprises/your-enterprise-id/devices/your-device-id'. Then go to 'Request Body' and use the '+' sign to add 'type' : 'REBOOT' as a parameter. Press the execute button, in which you will be prompted to choose an account for OAuth2.0. After this, you will see the results, and if successful (returns a 200 code), it will issue the reboot command, with the policy being updated after rebooting.
To reiterate, I know this isn't ideal, but it at least does do an update, so just providing that info.
Good luck and let me know if everything worked out.
It may take a while for the policy to sync and apply any changes, including removal of apps. You can force sync by opening the Android Device Policy app and touching the sync button. The other way is to issue a reboot command to the device to make sure that the new policy is applied. You can check the issueCommand method for more information.
I'm trying to find out what is wrong with my bot. This is a bot meant as back-end for a Cortana skill. The bot is built with the bot framework version 3.8.0. I'm running it on an Azure Bot Service instance (Azure Function).
Locally, everything works as expected. I'm using the bot framework emulator to test everything; all great. Now I publish the bot to Azure and invoke it using Cortana. Cortana replies there's an issue with the bot.
When I check the diagnotics log in Azure, I see the following:
2017-07-18T08:11:34.252 Exception while executing function: Functions.messages
2017-07-18T08:11:34.252 Invalid channel data.
2017-07-18T08:11:34.272 Executed 'Functions.messages' (Failed, Id=e5eae9f5-97e4-4a35-aa5f-5c7d58a63aed)
2017-07-18T08:11:34.272 Invalid channel data.
2017-07-18T08:11:34.272 Function had errors. See Azure WebJobs SDK dashboard for details. Instance ID is 'e5eae9f5-97e4-4a35-aa5f-5c7d58a63aed'
2017-07-18T08:11:34.272 Invalid channel data.
2017-07-18T08:11:34.315 {"id":"6f095c10-d9e8-4ad0-a6a8-caf052288f8b","requestId":"2f4c950c-2459-4467-8579-4f3b5bc45e6b","statusCode":500,"errorCode":0,"messsage":"An error has occurred. For more information, please check the logs for error ID 6f095c10-d9e8-4ad0-a6a8-caf052288f8b"}
2017-07-18T08:11:34.315 Invalid channel data.
2017-07-18T08:11:34.194 Function completed (Failure, Id=e5eae9f5-97e4-4a35-aa5f-5c7d58a63aed, Duration=4626ms)
2017-07-18T08:11:34.252 Exception while executing function: Functions.messages. Microsoft.Bot.Connector: Invalid channel data.
So "invalid channel data" seems to be the main error here, but that doesn't tell much. I enabled all logging on the server and downloaded + inspected these; there's nothing more useful in there.
I also attached a debugger to the remote process. I see my dialog method being called and finished without any problem. So the issue doesn't appear to be in my code, but in the framework somewhere? But I have no idea on where to go next.
BTW I also tried updating to the latest version of the SDK (3.8.5) but it appears that Microsoft.Bot.Builder.Azure has a dependency on version 3.8.0 cause it won't run after upgrading due to a assembly load error (it's trying to load 3.8.0).
You can debug your Azure published BOT locally. This will help you to find the real issue.
I am adding the steps how to debug Azure published BOT in locally.
Enable Debug in Azure Application setting:
Open Azure Portal.
Click on Azure Web Bot.
Click on Application Settings, In the Debugging section On Remote Debugging and select your Visual Studio Version.
enter image description here
Get Publish Settings:
Click on All App service Settings
Click on Get publish profile to get the publish setting with all user name and paths. It will download the settings.
enter image description here
Click on the Attach to process ..
enter image description here
In the Connection target: type your bot url without http://.
Example: yourbotname.azurewebsites.net:4022
--Click on Find Button.
--This is asking you to give username and password. You need to get your azure username and password from publish file.
enter image description here
Now run your Web App or Cortana to debug your BOT and the get real Error.
How do you link to your itunes review site in a Parse push message, is that even possible?
You have two options:
Option 1) First, create a custom activity in your app and all that activity should do is automatically open up the link to the whatever website/iTunes/app store product you want them to review.
Then, you can set your push notification via Parse to open that activity when the user clicks on it. See the section called "Responding with a Custom Activity" at this link. https://parse.com/tutorials/android-push-notifications
Option 2) At the same link, see the section for Responding with a Custom URI and simply use the URI to direct them to your website/iTunes/app store/etc. https://parse.com/tutorials/android-push-notifications
I am using the PushWoosh solution to present and send the notifications from my webpage to the mac users.
I would like to set my computer also as a test device where I could check and test my notifications.
To do this, the PushWoosh wants from me the device token of my mac. How and where can I get it?
Here you can see the screen of PushWoosh:
This paragraph in the "Notification Programming Guide for Websites" documentation seems potentially useful:
To check the permission level a user has set for your website, call
window.safari.pushNotification.permission() with your Website Push
ID as an argument. This synchronous call returns a permission object
for the given identifier by looking in the user’s preferences. This
function does not contact your server.
One of the items passed back in the permission object structure is deviceToken, which appears to be what you are looking for.