Share
Report
19Hi,
In an PowerApps application, we use the user's location and a destination address by clicking on a button to calculate the route that the user must take to reach this address (find below the formula).
Enable(Location);
Launch(Concatenate("http://bing.com/maps/default.aspx?rtp=pos.", Substitute(Text(Location.Latitude), ",", "."), "_", Substitute(Text(Location.Longitude), ",", "."), "~adr.", Substitute(Text(Concatenate(TextAdresseDetail.Text, " ", TextCodePostalDetail.Text, " ", TextVilleDetail.Text))," ","+"),"&rtop=0~1~0"));
Disable(Location)
During the development, this action was working well. But when we export/import the application to test it like a user, retrieving the user's location is not possible.
When we launch the imported application on a mobile (Android or IOS), PowerApps don't ask us for the location permission.
So, when we try to use our button, the application cannot use the user's location (longitude and latitude are empty).
But if we make a change within the application (even on something that is not linked with this action), publish the modification and launched one more time the application on mobile, then the location permission is asking by PowerApps and the action is working well after the agreement.
Furthermore, on desktop, using a web browser, even if PowerApps didn't ask us for location permission, the application is working well.
What's the difference between desktop and mobile ? And why does Powerapps need a udpate within the application to ask us for a location permission ?
Is this a bug in PowerApps side ?
All responses (
Answers (
