Any know vulnerability with targetSDK 22?
I was using targetSDK 22 with Android 5.1, since there are no more security updates release by googles for Android 5.1.
I just upgrade to my Android to 7? Will it address all my vulnerability as OS 7 will have latest security updates?
You should target the latest sdk available. You can keep your min sdk low but the target should be always updated.
Related
Oracle JDK 7 supports GCM since version 7u191 (https://www.oracle.com/technetwork/java/javase/2col/7u191-bugfixes-4489527.html)
In the openJDK Bugtracker, they mention they fixed it. (https://bugs.openjdk.java.net/browse/JDK-8200684)
But I checked with the latest OpenJDK 7 241 version, and still no AES GCM Cipher Suites. I need it in an old application for TLS 1.2 support with the GCM cipher suites. OpenJDK 7 btw. supports TLS 1.2 by default since a longer time.
I even checked the source code, but cannot find the backport commits. Is it an Oracle-Only fix?
I have developed a Xamarin Forms(.Net standard) UWP app and submitted it to windows store, but the windows store team reject the app because of the following issue.
The app doesn’t install on one or more of the currently selected device families due to an unsupported minimum OS version. If the affected device family is not intended to be targeted, then please de-select the unsupported device family and resubmit the app. Otherwise, please change the minimum and/or target OS version that the app supports (https://learn.microsoft.com/en-us/windows/uwp/updates-and-versions/choose-a-uwp-version#choose-which-version-to-use-for-your-app)
My apps min and target versions are Windows 10 Fall Creators Update(10.0; Build 16299). I am targetting my app only for windows 10 desktop devices and windows 10 mobile devices. So what is the correct min and target versions for my app?
To Martin Zikmund:
If I downgrade target version to 15063 (Creators Update) my windows app build failed with the following error.
The solution for this error is changed the target version to Windows 10 Fall Creators Update(10.0; Build 16299), I found it here. If I changed the min and target version to Windows 10 Fall Creators Update the build will succeed.
You are probably trying to traget Windows 10 Mobile, which did not receive 16299 (Fall Creators Update) and got stuck on a sub-FCU build. To support it, you would have to downgrade to 15063 (Creators Update), but that means you can no longer use the latest versions of Xamarin.Forms which are targeting .NET Standard 2.0 which is not supported on 15063 and have to downgrade to version 2.X of Xamarin.Forms. You will also have to downgrade your library from .NET Standard 2.0 to Portable Class Library.
Practically this means that to be able to use the latest and greatest of Xamarin.Forms you will likely have to drop support for Mobile and target the other SKUs only. Judging by the numbers it is probably a good idea nowadays, as most users are on Windows 10 Desktop, iOS and Android anyway.
I would like to ask that, how can I use the firebase cloud messaging to support my current minimum sdk version 9 of my app? Or should I use back google cloud messaging?
Thanks.
If you want to support Android versions < 14 you need to use Google Play libraries (or Firebase libraries) that have been released before February 2017 (version 10.2)
In February Google released Google Play services and Firebase 10.2 and changed the minimum required version of Android to 14:
https://developers.google.com/android/guides/releases#february_2017_-_version_102
Android version 2.3.x (Gingerbread) Deprecation
Google Play services 10.2.x is the first release that no longer
includes full support for Android version 2.3.x (Gingerbread). Apps
developed using SDK release 10.2.x and later require a minimum Android
API level of 14 and cannot be installed on devices running API
level below 14.
To learn more about your options, including building
multiple APKs to extend your app's support for Android Gingerbread,
see the Android Developers Blog.
using android studio 1.5.1
JRE 1.6.0
with the newest Android band sdk microsoft-band-1.3.20105.2.jar
developing on osx 10.11.2
targeting a galaxy not SDK version 22 (min version stated as 17)
trying to run the sample code
BandInfo[] devices = BandClientManager.getInstance().getPairedBands();
throws
UNSUPPORTED_SDK_VERSION_ERROR
What am I doing wrong?
Most likely the error message is "The version of Microsoft Health installed does not support this application. Please update to the latest version of Microsoft Health.".
So, all you should have to do is update the version of Microsoft Health you have installed on your phone.
Each new version of the Microsoft Band SDK appears to only work with the latest version of Microsoft Health, as it is that application that holds on to the Band's Bluetooth connection.
I am building an Azure app with Xamarin.Forms in Visual Studio 2015. My app is happily using both "Azure Mobile Services SQLiteStore" and "Windows Azure Mobile Services" in the Android and iOS builds. However, I am trying to get the same to build and run on WinPhone with little luck. I have tried various things, but typically end up with the following error:
Could not find SDK "SQLite.WP80, version=3.8.7.2". C:\Program Files
(x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1886
5 MyApp.WinPhone
Does anybody have a reliable set of instructions for getting Azure Mobile Services SQLiteStore operational on WinPhone 8.0 ?
In my case I had 2 problems
The reference to the SQLite for Windows Phone was missed in the WindowPhone App
As InitLipton said it's necessary to install SQLite for Windows Runtime depended on the windows phone version you are using (In my case was WP Runtime 8)
here are links of the runtime SDKs
WP Runtime 8
Windows Runtime 8.1