On Android 9, the requestPermission() method does not make appear the popup where user can grant or deny access to storage
As you probably know, since Android 6 it is necessary to do explicit request for permission to use Storage, Camera and others. Air SDK 24 introduced support for this new approach, through the requestPermission() method available in some classess (File for STORAGE permissiong, CameraRoll for CAMERA permission, ...)
Today I've discovered that the requestPermissiong() method in Android 9 does not popup the dialog windows where user is asked to accept or refuse authorization for STORAGE.
I don't know if the same problem is in Android 8 and 8.1.
For sure it works in Android 6 and 7 (I've tested it)
var file:File= File.applicationStorageDirectory
file.requestPermission()
In Android 6 and 7 (maybe aldo 8, I don't know) the code above popup the dialog windows where user can accept/refuse authorization to use storage.
In Android 9 nothing happens (the popup is not displayed)
NOTE: I'm using the latest Air SDK 32
I would suggest using a permissions ANE for better results. The AS3 was never reliable enough to use in apps. myflashlabs and distriqt, both offer solutions which work in any version.
Related
I feel like I'm missing something simple, but I am trying to upload my apk file thru Google Play Console. I keep getting the error message, " Upload failed Your app currently targets API level 24 and must target at least API level 26 to ensure it is built on the latest APIs optimized for security and performance. Change your app's target API level to at least 26." even though my target for the project in Adobe Animate CC says, "AIR 26 for Android".
The AIR SDK version is different from the Android SDK version. The version numbers appear similar but are not the same.
In order to specify v26 as the target SDK, add the following to your manifest additions:
<uses-sdk android:minSdkVersion="19"
android:targetSdkVersion="26" />
The AIR SDK contains a particular version of the Android build tools which is used as the default target sdk if you don't specify anything different in the manifest.
I believe to target Android SDK v26 you will need to be using at least AIR SDK v29.
I have an application built with the Titanium SDK that runs fine on iOS and Android. Now that Windows Phone can be targeted using Appcelerator Studio, I tried to publish the app to this platform. It published and ran but the app looks horrible and behaves unexpected and clearly needs some work.
When I search through Appcelerator's documentation for the Titanium SDK, the properties and methods for say "Ti.UI.View" do not have the Windows supported logo next to them? How do I know what properties and methods of the various classes are supported / I can use? I will post an example link below. It is for Ti.UI.View
http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.View-property-touchEnabled
Is there another source of documentation I am missing? Does anyone know if Appcelerator plan on updating their docs?
If the property does not clarify anything supports all e.g: BackgroundColor, but if the property supported only some are shown as follows: e.g BackgroundDisabledColor (Windows and Android)
I'm not sure if the documentation is up-to 100%
Documentation for windows:
Windows Phone specific UI capabilities
Windows UI Components and Conventions
I'm curious if it's possible for an app running on an Apple TV 4 / tvOS 9 to send HDMI-CEC commands to the TV. Specifically, I'm interested in if it's possible to change the TV's input to something other than the Apple TV.
I suspect that this isn't possible with public APIs in tvOS 9, but I'm curious if there are. And I'm open to private APIs as well. (This isn't for an app that I'm planning to submit to the app store!)
No this is not possible in tvOS 9.0
I added a uri association to my WMAppManifest.xml file in my Windows Phone 8 project and I'm able to successfully launch my app from within another app using LaunchUriAsync. I've also registered the same protocol in my Windows 8 project.
// windows phone 8 uri map
<Extensions>
<Protocol Name="myprotocol" NavUriFragment="encodedLaunchUri=%s" TaskID="_default" />
</Extensions>
On Windows 8, I am able to launch the app with by a simple hyperlink using my given protocol "myprotocol:".
On Windows Phone 8, I tried typing the protocol in the browser location bar, but I get an IE error saying this type of address is not supported. This makes me concerned I won't be able to launch my app from a web page simply by using my app specific protocol in the hyperlink.
Does anybody have any experience with this? Am I just paranoid?
fyi: here's the info on URI Associations in WP8
sometimes the simple answer is often overlooked.
Yes, everything is in place to function correctly. It appears to only be a restriction with IE Mobile.
I set up a web page on my server with a link click me and was able to successfully launch my app view IE Mobile on the emulator.
I am testing HTML5 geolocation code inside a WebWorks application for BlackBerry Playbook, using the 0.9.4 Simulator in VMWare Player. Here's the code:
navigator.geolocation.getCurrentPosition(geolocationSuccess, geolocationError, options);
Launching the application gives a popup saying:
Geolocation Request
local:// wants to access your location.
When I click "OK" this always results in a callback to the error handler function geolocationError, never the success handler.
The webpage works fine in Firefox 3.6.15 on Win 7.
Is there any way to test a successful geolocation request inside a WebWorks application in the Playbook simulator?
Updates:
Geolocation works in the Playbook web Browser, so you can test your application as a web page in the Browser.
I asked about this issue at a BlackBerry Developer Day and they confirmed this restriction. I asked them to publish a list of known limitations, they said they would look into it.
The simulator as of 0.9.4 still has no support for geolocation, according to the AIR SDK Release Notes. It's likely the same limitations apply in this case.