It seems that every single method or property of accessing BluetoothAdapter instance would cause crashes on Instant Apps, even with android.permission.BLUETOOTH and android.permission.BLUETOOTH_ADMIN are added to AndroidManifest.xml.
I know that I cannot find bluetooth releated permissions and operations here:
https://developer.android.com/topic/google-play-instant/getting-started/instant-enabled-app-bundle
I have also tried reflection way to trigger BluetoothAdapter.enable, but got InvocationTargetException.
Wondering if there are any other workarounds?
Thanks
You cannot use Bluetooth as an instant app.
The narrow list of permissible permissions shown at Supported permissions and operations give hint at the greater broad of the APIs that are restricted from being used in instant apps.
ACCESS_COARSE_LOCATION
ACCESS_FINE_LOCATION
ACCESS_NETWORK_STATE
BILLING – Deprecated as of Play Billing Library 1.0.
CAMERA
INSTANT_APP_FOREGROUND_SERVICE – Only in Android 8.0 (API level 26)
and higher.
INTERNET
READ_PHONE_NUMBERS – Only in Android 8.0 (API level 26) and higher.
RECORD_AUDIO
VIBRATE
WAKE_LOCK
If you try to use a restricted API as an instant app, it'll typically cause an exception (SecurityException, etc..) or some denial of sort.
Related
I am porting my Chrome extension to work in Microsoft Edge. I used Microsoft's toolkit and bridged the code. But i get an error is console saying "SCRIPT5007: Unable to get property 'contains' of undefined or null reference". This is thrown at the place where i have called chrome.permissions.contains.
Let me know if there is a solution for this or if there is a documentation for all these incompatibilities.
The API is not currently supported by Edge. Microsoft lists it as "Under consideration".
So the only solutions are:
Do not use chrome.permissions in your port. Probably by granting the widest permissions possible. Unpleasant, but you have to explain to users that it's a platform limitation.
Wait until it is supported (which is not guaranteed; FF's WebExtension platform doesn't support them yet either).
The roadmap of API support is here: Microsoft Edge extension API roadmap
Detailed list of supported APIs with known issues/incompatibilities: Supported APIs
I am having trouble finding a NoSQL databases that officially support MonoTouch via a local DB on the device. If their are, could someone provide a list of them here.
According to http://nosql-database.org/ there's siaqodb. Note that others might support MonoTouch without being mentioned in that site.
Edit: a few more clicks shows that HSS Database (from the same list) also supports MonoTouch.
You might also want to look at which ones support iOS (e.g. with Objective C) and see if bindings are available (or write your own).
Take a look on Couchbase Lite xamarin's component
RavenDB supports an embedded mode, and can run on Mono using the "Munin" storage engine option.
Although, there has been talk in the user group lately about dropping Munin, and it's not usually recommended for production, so it may not be a viable option.
I've not heard of someone using it with MonoTouch specifically, but there are some running it on Mono. If you try it, please update comments here with your findings. Thanks.
A bit late, but still relevant:
I'm the author of MarcelloDB, and I just released version 0.3.0 on nuget.
MarcelloDB is a document DB, built specifically for mobile apps (light-weight, low memory usage) and supports Xamarin Android and iOS as well as the windows platform.
I still have some features I want to add before reaching v1, but the file format and existing api are allready quite stable.
Is it possible to get the phone number of a incoming call and record it using Windows Mobile 7.0 or later versions. I have tried OpenNETCF.IoC(1.0.12221) but i could not find a way to do it.Wasted about 2 days searching for this.If somebody can help me out it would be a great help . Simply the app must be able to detect the phone number of the incoming call
No, it is not. There are no Windows Phone APIs for handling calls. Microsoft have supplied a deliberately restrictive set of APIs so that developers cannot interfere with the core phone functions.
Write it for Android and run it on Windows in a couple months. That's what most of the WP developers I know plan on doing. Android "intents" handle this scenario very well.
Since straight Java development isn't going to be supported on BB10 (Am I right?), at least not without using the Android Java Runtime (which I don't want to use), I'd like to know if there will be official support and an official API from RIM for accessing and writing on the Secure Element of the upcoming BB10 handsets. I'm a developer who's considering the BB10 platform for developing an application which will need read/write operations on the Secure Element. Would that be possible? Would I be needing special permissions and/or keys from RIM?
Apparently there's not much documentation on the subject so far.
They have removed the SE on BB10 and left only the UICC...And we feel it's a good thing, as there were loads of issues with accessing the SE of a SIM
After some posting on other forums, I learned that there is indeed an API for accessing the SE in the upcoming BB10 platform. It was included in the BlackBerry 10 Native SDK (Beta 2). So far, it seems it serves my purposes.
Your best bet would be to go to the RIM issue tracker site, you can get access if you make an account at the BlackBerry Jam Zone. Submit an issue under the BlackBerry 10 project making the business case for what you want to do. They may be able to tell you what their plans are, but there is still some mutability in the road map if you can make a strong enough case.
While I'm no expert on iOS development, I have read through the API docs on Apple's developer site and I can't find anything on this. Before I presume that it's impossible let me ask here: Can I somehow monitor application launches on a standard iOS device? By "standard" I mean not jailbroken and using only public iOS v4 APIs. Any insight is appreciated. Thanks.
No, there's no access to system-level stuff like that at all. The somewhat-small sandbox makes certain types of apps impossible, but does provide a lot of protection for the user.