I am trying to build an aenter image description herepk (mobile application) using xamarin for detecting the outgoing calls, the functionality are working good, but the issue i am not getting displayed any permission when installing in my mobile.
From android 6.0 runtime permissions are introduced and apps no longer require any special permissions during installation.
Read this article here
Many Custom ROMs or skins like MIUI have already included runtime permissions mechanism for lower android devices (below 6.0) as well
Related
Currently,
My team and I are developping an Android Auto enabled app. And it appears to me this app is only available in my car unit, when I enable unknown sources in the Android Auto app.
However I'm wondering what defines an unknown source and how do I make sure my app is not an unknown source. Does Android Auto communicate with the Google Play Services for this or do i need to sign the APK with specific data?
How are you deploying your app? If you are deploying with Android Studio: as I recall you won't see it on your real automotive head unit, just the emulator. To show on the head unit it needs to be deployed in the Play Store, at least in developer and pre-release mode while under development.
First of all: Android Auto runs on your own device, meaning it adapts the same permissions you granted to particular apps. If your app doesn't have an app in the normal UI or you didn't open it on your phone once, then it would usually prompt you to grant permissions the first time you open it.
An unknown source is pretty much any way of getting your app outside of the Google Play Store (and OEM-specific app stores like Samsung App Store for Samsung devices etc.).
That is especially common if you e.g. download an .apk from the internet and want to install it, but your phone thinks their own file manager is an unknown source (because it is not intended to download apps).
I have added desktop extension to my UWP app that gives some extra functionality if it runs on Windows 10 desktop platforms. But for other platforms it won't be used. Hence I want to make sure that the desktop extension isn't installed on other platforms thereby saving users some disk space. I have looked into app extension but it won't be viable for my use cases since the UWP app and desktop component communicate via named pipes and memory mapped files. Is there any other way I can control the installation of desktop component depending upon the platform it is being installed??
Update 1
From researching further I have found that this should be possible with optional packages/related sets, to be accurate related sets for my scenario. The examples provided in docs only show scenarios for packaging uwp apps as related sets and no example for packaging win32 apps as related sets was given. Is there any way to package a win32 application as related sets??
I have an older application that I've converted using Microsoft's "Desktop App Converter" to create a UWP application. The application appears to convert fine, and I can install and run it on my local machine. Unfortunately, when I try to submit the application to the Windows App Store, I get the following errors:
Package acceptance validation error: We don't allow the capability you've specified: runFullTrust.
Package acceptance validation error: You don't have permissions to specify the following namespaces in the appx manifest file of the package DownloadManager.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities.
Are there any ideas what is causing this and what the fix is?
I'm running Windows 10 Enterprise Preview Version 1511, Build 14352.1002
According to this article from the official blog, you cannot submit your Centennial apps to the Store just yet. You have to follow the process they mention in their article:
Windows 10 Anniversary Update SDK Now Available! Windows Store Open for Submissions
"Windows Store Open for Submissions; Including Process for Submitting Desktop Bridge Apps:
In addition, we will begin the process of accepting apps using the Desktop Bridge. While we build the pipeline into the Windows Store to publish these apps, our team will work directly with developers to get their converted apps and games into the Windows Store. Contact our team here if you are interested in submitting an app using the Desktop Bridge to the Windows Store."
You can find in this article Preparing your desktop app for conversion to UWP features that should be removed from codebase.
As I see there is one Your app always runs with elevated security privileges.
Check this one ar may be your app contains some another feature from list
Scenario:
Our company wants to develop a mobile application.
Our customers use a web application, which for the most part is hosted at their own servers.
This mobile application will be shipped at the same time as our web application, to make sure that they are compatible with each other at all times without careful mainteanance.
Thus i have to ensure that mobile applications can be distributed in a versioned manner (which is not that easy on every platform).
My question: Is it possible to build, host and distribute(install) mobile applications for windows phone, ios and android?
Research results so far:
1 VERSIONED INSTALL
Windows phone : probably*
IOS : probably*
Android : yes*
Notes:
IOS: Possible from special app store (along the lines of this)? Either they get build products from us and deploy it in their version of the store or we host it for them.
WP: I GUESS similar option to ios?
Android: Allow unsafe sources + install url. (see this)
2 BUILD:
Windows phone : probably
IOS : probably
Android : probably
Notes:
I'm guessing here, since i didn't start a trial yet, but i suppose depending on platform i can execute a build and receive executables (exe, apk, whateveriosextensionis) which can then be distributed
3 VERSIONED HOSTING
Windows phone : yes*
IOS : yes*
Android : yes*
Notes:
WP: According to this and this - possible
IOS: According to this - possible
Android: Host version at url of choice - should be simple enough? (like this link indicates)
Is my research on this topic correct? Does anyone have experience with the subject and would be kind enough to confirm? Right now my conclusion would be that it looks like it is possible for all 3 platforms.
I followed the documentation(https://parse.com/docs/dotnet/guide#push-notifications-setting-up-push) by Parse for sending Push to Windows 8.1 device. But, I am not able to get through the first step ie. "Installation". As per the documentation I followed , the channel should get registered instantly. I have enabled "Toast capable" within the Package.appxmanifest file in my Windows 8.1 Universal App(C#).
I have also authenticated the App by adding the Package Security Identifier and the Client Secret to the Parse.com Windows Push Credentials settings. But still no success. Can anyone tell me if I am missing anything or if Parse SDK is supported for Universal Windows 8.1 C# App.
I previously had Parse working for WP8 as per instructions here. So this is to say it is definitely doable, follow those steps there to see if you missed any steps.
Caveat
We are using Cordova, but I had to end up doing this part natively. It was working in December 2015 but mysteriously this year we had issues with Parse on all 3 device platforms (iOS, Android, WP8). I'm still spending time trying to figure out why WP8 just doesn't work now, can't even get the device to register to a channel anymore...