I wanted to develop an application. What shall I consider to select my target android version (minimum version requirement)?
You can follow this link
<uses-sdk
android:maxSdkVersion="21"
android:minSdkVersion="9"
/>
you can use like this in AndroidManifest.xml
Related
I've got a BackgroundTask which should be Extended with the ability to Play Music. Therefore, i Need to include this capability into the Package.appxmanifest-file. As soon as i include the capability
<uap3:Capability Name="backgroundMediaPlayback"/>
in the Package-Capabilities-section i get a Validation error stating the my app manifest must be valid as per scheme. If i remove the line above, everything works fine. My package node is as follows:
<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" xmlns:uap3="http://schemas.microsoft.com/appx/manifest/uap/windows10/3" IgnorableNamespaces="uap mp iot uap3">
I searched the web and found out that this could be a bug in Visual Studio, but it should be fixed from Version 15.2 on(https://developercommunity.visualstudio.com/content/problem/44306/package-an-uwp-project-with-capability-of-backgrou.html).
Nevertheless, i am not able to compile the app including above capability. I did also a repair of my VS2017 Installation, but it did not help. The app is targetting the Windows 10 fall creators update (10.0; build 16299) for both, min and max Version. It is designed to run on a raspberry pi.
Do you have some clues?
EDIT: The BackgroundTask has been created using the downloaded template from https://marketplace.visualstudio.com/items?itemName=MicrosoftIoT.WindowsIoTCoreProjectTemplatesforVS15
Referring to this post
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/8efde534-f84a-48d7-9dd5-fec5043a894c/uwphow-to-use-a-restricted-capability-?forum=wpdevelop
it seems it is necessary to Keep a certain order. However, moving the uap3-Capability before the DeviceCapability solved my Problem. Strange, isnt it?
For example: My Xcode project deployment target can be iOS 10.3 — Is there an equivalent to require macOS 10.12.4? (Latest SDK)
• iOS 10.3 is the latest update (can be targeted in Xcode).
• macOS 10.12.4 is the latest update
My goal/hope is to target the latest macOS update in the same way I can target the latest iOS update.
Verdict: It’s not (yet?) possible in Xcode. :(
While building you can define a deployment target. This is a specific API level for the minor versions of the operating system. This will run on all patch level versions for this particular minor version. So there is little point to set deployment targets on patch level.
You can check that you run your applications on certain operating system versions only though with a little code.
operatingSystemVersion and isOperatingSystemAtLeast(_:)seem to do what you want to achieve:
https://developer.apple.com/reference/foundation/processinfo/1414876-isoperatingsystematleast
You can then exit and deny using the application if the desired criteria is not met.
P.S. iOS deployment lets you chose iOS version 10.3 only too. There is no specific option for iOS 10.3.1 for example.
Can't you select such an option when you set your deployment target?
The page linked to also states:
Xcode sets the Minimum System Version key in the app’s information
property list to the deployment target you choose. When you publish
your app to the store, it uses this property value to indicate which
versions your app supports.
So you might change it by adapting the information property list as well I presume..
I was able to set a minor release version by editing my project's project.pbxproj file, located within your xcodeproj bundle.
Once you've located your project.pbxproj file, open it and
search for MACOSX_DEPLOYMENT_TARGET. You can set its value to any valid macOS version (no quotes needed).
The result is correctly displayed within Xcode's UI, and most importantly, is respected when compiling. I've confirmed this by using #available directives.
I am trying out new versions of the project tango c++ examples from github
but I'm having problems running them.
I get the error:
"Installation failed with mesage INSTALL_FAILED_MISSING_SHARED_LIBRARY"
when trying to run the example in Android Studio.
I suspect this is related to the service migration. If I try to change
<uses-library
android:name="com.projecttango.libtango_device2"
android:required="true" />
to
<uses-library
android:name="com.projecttango.libtango_device"
android:required="true" />
it builds, but I get the error when starting the application:
"Tango Core out of date, please update in Play Store"
There does not seem to be a any newer version of Tango Core for the Mira update in the Play store, might this be the problem?
For reference, I'm running on Ubuntu 15.04, and I've also changed the Application.mk according to this issue : https://github.com/googlesamples/tango-examples-c/issues/70
Please check
https://developers.google.com/project-tango/release-notes
The BSP OTA updated will including the libtango_device2 library.
Also The Mira release examples code have a version check, which need downloading Mira TangCore from PlayStore.
Mira releast TangoCore is out. please check your Playstore for updating your TangoCore.
Thanks.
with titanium appcelerator, how do i specify I want to use version X in my project?
how do i know which is the latest version of Appcelerator that I have to use?
Oho.
So in the tiapp.xml file there is this entry:
<ti:app xmlns:ti="http://ti.appcelerator.org">
... other stuff here
<sdk-version>3.1.1.GA</sdk-version>
You'll be wanting to edit that value to the value of the titanium sdk you'd like to use. I uh, i don't quite understand why the "GA" is there, but that appears to be on all the 3.X version\
As for the latest version, i'm unsure. I don't know quite how to check what version you have available.
As for what version Titanium is up to, go to the titanium api homepage and then select the link "QuickStart" - it is a tab-like thingy.
On that page, search for the words "compatibility matrix", and click on that link. I didn't post the link because the simple folks who mind the Titanium website might change it.
On that link, there are a few tables listing what version of the sdk needs which version of android/ios etc. You'll find the latest version they're using there.
Good luck, warrior.
Alright what I noticed is that when I am developing against iOS 4.3, and I set my deployment target as iOS 4.1, I DO NOT get any kind of warning from the IDE about calls which are not supported in the minimum deployment target.
For example, calling [CLLocationManager authorizationStatus] shows no warning, despite the fact that the documentation for authorizationStatus says it was implemented in iOS 4.2.
I expect this would be a problem when wouldn't it?
From what I understand the solution to this is to download multiple SDK versions, temporarily build against the SDK for your minimum version, but switch to the current SDK version in order to ship.
If there is a better way to do this please advise. How can I get more options in Xcode under the "Base SDK" setting?
I expect this would be a problem when wouldn't it?
Yes, you'll generally crash if you call a method that doesn't exist.
From what I understand the solution to this is to download multiple
SDK versions, temporarily build against the SDK for your minimum
version, but switch to the current SDK version in order to ship.
That's a pretty good approach; probably the best way to find this kind of error semi-automatically.
If there is a better way to do this please advise. How can I get more
options in Xcode under the "Base SDK" setting?
You don't install all the SDK's together in a single "Developer" folder. Install each one separately -- there's an option to choose an alternate location when you install the SDK. Then it's just a matter of finding the copy of Xcode in the right folder and launching.
You don't need to have multiple options under Base SDK -- the normal practice is to just use the latest, but set the Deployment Target to the minimum version of iOS that your app supports.