Part of the upgrade steps for moving to Corda open source 4.3 are to use Gradle 5.4.1 https://docs.corda.net/docs/corda-os/4.3/app-upgrade-notes.html#step-2-update-gradle-version-and-associated-dependencies
Does Corda require this precise version of Gradle or can a later version be used. For example: could 5.6.4 be used instead?
If later versions of Gradle can be used how can developers know what maximum version of Gradle is compatible with Corda?
You should be able to use Gradle 5.6.4 with Corda, although nothing higher as the Gradle plugin for Kotlin 1.2.71 is incompatible with Gradle 6.x.
Corda is currently constrained to use Kotlin 1.2.x both by its dependence on Quasar and by a change to Kotlin byte-code that was introduced in Kotlin 1.3.40. We are working to resolve this.
Related
is there a way to know when a version of Flyway is going to get deprecated?, actually we were using 6.0.7 the last year and then got deprecated like 6 months ago, now we are using 6.4.1 but I tried to find something on the blog and documentation but there's nothing about some news of when a version is going to be deprecated, only when we run our java spring boot project we know that a version is not usable. And we're aware of this because there's a lot of changes in version 7+ that doesn't work with our project (tested version 7.0.1 and the app crashed) and we need to estimate the cost of the changes.
Any help would be appreciate, thanks.
Flyway releases via Maven OSS. Old versions are kept indefinitely and are outside of Redgate's control. In theory, all older versions which are currently available on Maven will continue to be available for all time.
Newer versions may deprecate features over time, but older versions will always be available.
I'm trying to add Firebase authentication to my app. I've gone through the process of linking firebase with my app, but when I get to Step 4.6 and try running my app with the Firebase plugins installed, I get the following error:
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_core-1.0.2\android\src\main\java\io\flutter\plugins\firebase\core\FlutterFirebaseCorePlugin.java uses or overrides a deprecated A
PI.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_analytics-7.1.1\android\src\main\java\io\flutter\plugins\firebaseanalytics\FirebaseAnalyticsPlugin.java uses or overrides a depre
cated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_auth-1.0.1\android\src\main\java\io\flutter\plugins\firebase\auth\FlutterFirebaseAuthPlugin.java uses or overrides a deprecated A
From what I understand, I need to wait for the Firebase team to update their plugins before I can use them with the latest version of Flutter
Flutter 2.0.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 8962f6dc68 (2 weeks ago) • 2021-03-11 13:22:20 -0800
Engine • revision 5d8bf811b3
Tools • Dart 2.12.1
Does anyone know the latest stable build that the Firebase API works on? These particular errors don't stop the build from completing, however if I try to use the playstore plugin, for example, it crashes the build script. For now I'll try to find a compatible stable build myself. I'll update this post when I find it.
Latest stable flutter build is 2.0.3. Many Firebase plugins have been migrated already to null-safety. Everything is working as a charm for me while using latest versions of dependencies for Firebase from Pub.dev, even for flutter web.
I think it might be something in the play-store plugin implementation however.
I want to implement Push Notifications in Xamarin.Forms.
It appears I need to use the NuGet package Xamarin.Firebase.Messaging - as referenced, for example, in this tutorial:
https://www.youtube.com/watch?v=le2lDY22xwM&t=1s
However, if I try and add this package to a vanilla Xamarin.Forms app, I get this error:
Package Xamarin.Firebase.Messaging 71.1740.0 is not compatible with netstandard2.0
I found this about this error, it's 2 years old but isn't really helpful:
https://forums.xamarin.com/discussion/86307/xamarin-firebase-not-compatible-with-forms
I also can't comment on that post as the login appears to be broken.
How can I fix this error? (as an aside if anyone has a better suggestion for sending cross platform notifications in Xamarin.Forms I welcome it, I've tried AppCenter.ms but couldn't get that working either).
Thanks.
I would recommend you to follow this tutorial here.
You don't need to to install specifically version 71.1740.0. You can just install version 60.1142.1 and it works too.
This issue is mainly caused because of dependencies to Xamarin.Android.Support nuget packages and the Target Framework in your Android project.
On this page you can find all dependencies related to Xamarin.Firebase.Messaging nuget package. If you go through dependencies of version 71.1740.0 you find that you need to set Target Framework to Android 9 in your project. See picture bellow.
To install latest Xamarin.Firebase.Messaging into Xamrin.Forms vanilla project you just need to change this Target Framework to Android 9.
However, if I try and add this package to a vanilla Xamarin.Forms app, I get this error: Package Xamarin.Firebase.Messaging 71.1740.0 is not compatible with netstandard2.0
According to your description, you only install this package into a Xamarin.Android project as there are no targets for this NuGet package to install into a PCL.
Look at the "Dependencies" on NuGet,In this case, only MonoAndroid90 is supported. This is synonymous with Xamarin.Android targeting API 28 minimum. So please check Compile using Android version:(Target Framework) and Target Android version is Android 9.0.
My build.gradle is:
// for facebook account kit
compile 'com.facebook.android:account-kit-sdk:4.+'
// for google firebase database
compile 'com.google.firebase:firebase-database:9.6.0'
// for google firebase cloud messaging
compile 'com.google.firebase:firebase-messaging:9.6.0'
After rebuild project，a error happens.
Error:(74, 27) error: Cannot access AbstractSafeParcelable
Cannot find
com.google.android.gms.common.internal.safeparcel.AbstractSafeParcelable class
==============================================
Resolution:
The reason is that after rebuilding the project, gradle download the latest version of "account-kit-sdk" to 4.25.0, the new version changes some about gms, so make some conflicts with firebase messaging,
So I downgrade the account-kit-sdk version, change import version from "account-kit-sdk:4.+" to "account-kit-sdk:4.24.0"
Then the issue has been resolved.
But I think it is not the best resolution about this problem.
Welcome friends add some new ways to resolve this issue.
Thanks.
Version 4.25.0 of com.facebook.android:account-kit-sdk has a dependency on com.google.android.gms:play-services-auth-api-phone:11.0.1 that is not present in version 4.24.0. com.google.android.gms:play-services-auth-api-phone adds many transitive dependencies on other com.google.android.gms modules, including base, basement, tasks, auth, and auth-base.
The Firebase libraries also have transitive dependencies on numerous com.google.android.gms modules. If the version numbers of all of the Firebase and Play Services modules in a build are not the same, problems such as this one occur.
A simple solution is to use version 11.0.1 of all Firebase and Play Services libraries you list in your gradle dependencies:
// for google firebase database
compile 'com.google.firebase:firebase-database:11.0.1'
// for google firebase cloud messaging
compile 'com.google.firebase:firebase-messaging:11.0.1'
You should also specify a fixed version number for the Facebook library to make your build predictable and repeatable:
compile 'com.facebook.android:account-kit-sdk:4.25.0'
The risk of specifying the version as "4.+" is that when a new version is released that has transitive dependencies on a new version of the Play Services libraries, the new Facebook lib version will be automatically used and your build will break again.
To debug problems like this one, you can open the Gradle window in Android Studio and double-click on :app -> Tasks -> android -> androidDependencies to generate a dependency tree. The tree can then be examined to find version mismatches.
So I updated to swift 3.0 and now my projects with realm 1.0.2 all give me an error.
RealmSwift compiled with older version of Swift language (2.0) than previous files (3.0)
I also tried to build a net new project and still get the build error, so I know it is not a conversion issue on the Swift side.
I found several Swift 3.0 beta users and tried to run the script to update my version to 3.0 and several other options. The last few posts appeared to use Cocoa Pods - which I don't currently use. Is that the supported fix path?
Any help or direction would be greatly appreciated.
I haven't tried it yet, but here is what should work.
Essentially, the compiler gives you a description of what went wrong. The framework was compiled with Swift 2.0, while your project or other files were compiled with Swift version 3.0 (which means you made the switch after upgrading to the new version of Xcode.
To fix this, you need to use the Realm framework compiled with a Swift 3.0 compiler. Since the Realm team doesn't yet provide a precompiled version compiled with Swift 3.0, you have to do so yourself. To do that, go to their Github repository, and follow the instructions in the README under "Building Realm":
Prerequisites:
Building Realm requires Xcode 7.3.
Building Realm documentation requires jazzy
Once you have all the necessary prerequisites, building
Realm.framework just takes a single command: sh build.sh build.
You'll need an internet connection the first time you build Realm to
download the core binary.
This should generate the Realm framework with the current compiler version, which you then just have to use to replace your current Realm framework with. After that, everything should compile as it used to.
As stated before, I don't know if this actually works, as I haven't tried it yet. I don't exactly know if Swift 3.0 is supported by Realm yet or if there are any other issues you could run into. So please let me know how this works out!