When I try to upload a beta version of a Tizen wearable app to the Samsung Galaxy Store Sellers Portal, I get an error:
The VersionCode is invalid. VersionCode must be entered in integers and the same version number cannot be used for more than one binary.
I already have a beta up, and am trying to upload a newer beta for the same 1.0.0 version of the app.
In my tizen-manifest.xml file, I specify version="1.0.0" but I can't figure out how to specify a "VersionCode" or "Version Code".
<manifest xmlns="http://tizen.org/ns/packages" api-version="4" package="org.company.tizen.MyCoolTizenApp" version="1.0.0">
My current beta shows what you see in the image below when you view it in the Samsung Galaxy Store Sellers Portal.
How does one set the "Version Code" for a Tizen app? If it matters, I'm using Visual Studio to build a .NET based Tizen app.
For now I just have to delete the beta that's up and upload the new one that has the same "Version Code" that I'm unable to change. I can't find this documented anywhere, and searching through the depths of Samsung developer forums has not been helpful.
It is alright, just change it to 1.0.1
As far as I know, there is no way how to update it with the same code. This is the only way.
It's just totally my inaccurate guess, but the error message possilbly refers the Version Name? not the Version Code.
Related
As you already know that
"Beginning Jan 23, 2018, Google Mobile Ads SDK versions older than
7.0.0 for Android and 7.0.0 for iOS will no longer be supported".
Above statement mean this ? ===>
"compile 'com.google.android.gms:play-services-ads:10.0.1'"
I am confuse that I am using correct Google Mobile Ads SDK Version or not? OR I need to check something else?
No need to do anything, you already using 10.0.1 version which is greater then 7.0.0, however you can update to current latest version which is 11.8.0.
Google Mobile Ads SDK offered for Android through Google Play services which is available from the Google maven repository.
Google Mobile Ads com.google.android.gms:play-services-ads:11.8.0
Google Mobile Ads API dependency injection
apply plugin: 'com.android.application'
...
dependencies {
implementation 'com.google.android.gms:play-services-ads:11.8.0'
}
Does NXP i.MX7D support Google Cast via Android Things?
Android Things Version: Developer Preview 6.1 which has 11.6.0 Play Services.
We need to show the UI on external displays like TV with Android Things, but the Google Cast feature does not seem to work with Chrome Cast.
To Test the code we manipulated our source code, so that it can run on Android Device; which runs perfectly fine. But when we try it on Things, it does not discover any devices to cast.
We also tried similar procedure with the Google Sample - CastRemoteDisplay-android
The above sample works on Android Devices but the same does not work on Android Things 6.1 developer preview; after making required changes to run on Things
We also tried different Play Services versions from 10.x and 11.x
We also tried to change the API level from 23 to 27
But all results the same
NOTE: I am not including any code or stack trace as I feel it is not required. But if any one demands will post the required logs
After lots of trial and research, I found out that the version of Play Services installed on Things Developer Preview 6.1 does not support it. It lacks GMS Core, because of which currently not possible.
In the mean time I'll try to search and side load OpenGapps with GMS Core, but I am not sure if it will work
In Android Studio 3 "Add Module" no longer as the option to add a Google Cloud module such as Cloud Endpoints. - How can we add an Endpoints module (and firebase for example) now?
According to the docs it is not supported in Android Studio 3.0
#jkaps9 I believe this to be the case since I have been trying to set up Google Cloud Endpoints for the last week & a half. Despite everything I have tried, that is, following Google's instructions and or some tinkering, it just won't work.
I realized however that I did upgrade to Android Studio 3.0 which says "however, your existing projects with cloud backends will continue to work in Android Studio." I now thinking that it's affecting the setup/project.
When deploying an existing Xamarin forms proj from Visual Studio I was getting errors like "Failed to load AOT module ‘System.Net.Http’ while running in aot-only mode". This had worked in the past, it seemed Xcode had recently updated before I hit the problem. I found I was able to get the project deploying by changing the csproj entry 10.0 to 10.3. It looks like I could change this setting and everyone would be ok if they also had updated xcode.
My concern is: Does this change what versions of iOS the application can support? Would it have any other surprises when deployed to the apple store?
One thing I don't understand is I am the only person seeing this issue. Another developer is able to deploy to an iOS device (iPad instead of an iPhone) that also has the latest version of iOS without problems. Running “xcodebuild -version” shows we have the same version of xcode installed (8.3.1) and running “xcodebuild -showsdks” shows we have the same iOS sdk available (iOS 10.3).
There is some good documentation on the iOS SDK version: https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/cross_development/Overview/overview.html#//apple_ref/doc/uid/20002001-BABEBGCF
You can build against a higher version of the SDK and run against lower versions of iOS.
Building against different versions of the iOS SDK can cause differences in behavior, these may show as regressions in your application.
I have an Android Wear app that I'm trying to migrate from Eclipse to Android Studio. It's working (more or less) on my LG G Watch, but when run on my Moto 360 I get the following message in logcat:
GooglePlayServicesUtil﹕ Google Play services out of date. Requires 6111000 but found 5091534
followed immediately by Connection to Google API client has failed. Running on the emulator gives a similar message:
GooglePlayServicesUtil﹕ Google Play services out of date. Requires 6111500 but found 5077534
It strikes me as odd that the Requires version is slightly different in each case, but there you are.
I've been through the similar questions here on SO, and the answers usually boil down to ensuring that the module's Gradle dependencies are using play-services-wearable rather than just play-services. I've checked this and it appears to be correct; here's the relevant section from my build.gradle file:
dependencies {
compile project(':wearableCommon')
compile 'com.google.android.support:wearable:+'
compile 'com.google.android.gms:play-services-wearable:+'
}
Note that wearableCommon is a library of my own, containing code I'm using in several wearable projects, and it doesn't use GMS.
I'm particularly bothered by the fact that this works on one device but not another. If I didn't have the 360 in-house, I might well have released this code after testing it on my G Watch. I would have then been in the position of trying to debug this in the wild, while simultaneously doing damage control for hundreds of angry 360 owners.
Easiest "fix":
Set your play-services-wearable to specifically look for 5.0.77
compile 'com.google.android.gms:play-services-wearable:5.0.77'
More info:
https://plus.google.com/u/0/101581283591300788111/posts/5bHfmjtvQ6R
I literally had this exact same problem. Wayne is trying to help me out with it. Join the discussion if you like.
The latest version of Google Play Services was rolled out to Android Wear devices recently. The latest SDK update for play-services-wearable requires that your wearable is updated, which is shown in the error message that you report. Make sure you have the latest companion app installed on your phone, and it will install the update to your wearable as well. Make sure that you have your wearable paired with your phone, otherwise it will not be able to update the wearable!
If you have your wearable paired with your phone, these things will automatically update and there should be not be a problem.
I would not recommend hard coding your build.gradle to 5.0.77, because then you will never update to use the new APIs for Play Services.