How To Solve Gradle Build Failed Error -Unity - firebase

I am using Firebase Auth. I am working in unity 2018. I have dowloaded Quickstart-unity-Master. In that I am working Auth Section. I have download the latest googlservices.json file also, but when I try to build the Firebase auth in android, it shows the error
Gradle build Error.
Error Image
I have searched in Forum it Says Java greater 8 is not supported. I am using jdk1.8.0_171.
I have donwloaded varrious unity packages 2017 Versions.
I Installed 10 Different versions. In that one versions First time it builds and apk produced. But second time I build it shows the error. Gradle Build failed.
How can I solve the gradle Error.
Thanks and Regads

This error might not be related to Firebase at all. I have multiple projects where Gradle fails for some reason. Just try what happens when you switch the build system from Gradle to Internal. This works for my projects.

Related

Why does WebAssembly fail to build on fresh Uno Platform template

Summary:
When I attempt to build and run my Uno WebAssembly on Ubuntu 20.04, it fails. The error cites a file or directory that doesn't exist.
Steps to reproduce:
Open Ubuntu 20.04 platform
Install .NET Core SDK 3.1.403
Follow the "Getting Started on VSCode" tutorial here
When you attempt to start the app with the .NET Core Launch configuration, note that the build fails.
Error Details:
/home/<user>/.nuget/packages/uno.wasm.bootstrap/1.3.4/build/Uno.Wasm.Bootstrap.targets(126,2): error : System.ComponentModel.Win32Exception (2): No such file or directory [/home/<user>/Projects/uapp/uapp.Wasm/uapp.Wasm.csproj]
What I've tried
My knowledge of Uno Platform is approximately 1 day old. I'm not sure I understand enough about it to even know what to try, but I have done these things:
Run dotnet run from within the uapp.Skia.Gtk, which successfully opened the window I expected to see.
Run dotnet run from within uapp.Wasm, which resulted in the error described above.
Look on the documentation for clues on why the file might not be found on a fresh template that's not been modified (I could not find anything)
Question:
What should I be doing differently to get the Web Assembly to build and display the app correctly?
EDIT: The file in the error does exist, precisely in the path in the error.
You're hitting an error that may happen when building with some native components, like SQLite or Skia.
To fix this, you'll need to execute the dotnet-setup.sh installation script which is not yet run automatically.
This script installs .NET Core, mono and ninja, on ubuntu-alike systems.

Firebase Crashlytics For Xamarin iOS- Missing dSYM files

Need Help !!
We are getting caution message on top of the Dashboard in Firebase Crashlytics. We are tried with different technical advises in different forums.
But nothing has worked out for us. We are still seeing the caution message at the top (in red strip) and crashes count is incrementing on every crash but doesn't come to Dashboard.
Here we go with our Firebase Crashlytics integration with project :
We are using Firebase Crashlytics with Xamarin Forms project to record any crashes in Mobile Application.
Since, Firebase Crashlytics SDK & Documentation are mostly on Native Platforms (Android & iOS). But, we still got provision to get packages from NuGet.
Here is the checklist which ensures we are on right direction:
1) Is App released with proper Apple Distribution Provision Profile and Certificate- YES
2) Is Distribution Provision Profile valid in terms expiration date - YES, it is valid till Next year from now.
3) Is GoogleService-Info.plist correctly placed. YES- it was downloaded from Crashlytics console with proper identifier configured. File was placed at root of iOS Project and set Build Action as BundleResource.
4) Did we call required initialisation function at proper place. - YES. Below set of codes ensures we initialised properly Firebase Crashlytics in AppDelegate.cs class.
5) Is your build configuration rightly placed in Release mode. YES
6) Important Point: Firebase Crashlytics was able to process the reported crashes with earlier version of iOS build which were having same project and package configuration and we could able to see the Crashes in readable format till for immediate previous versions.
But suddenly it stopped working when we promoted to production in AppStore (means LIVE in AppStore)
7) Have we uploaded to dSYM file manually to Firebase Crashlytics - YES we TRIED. We followed the steps to upload dSYM using XCode-SWIFT project with POD files.
Here is the setup and step.
POD was installed in appropriate XCode workspaces.
Run Script was executed with recommended POD commands.
Build was succeeded.
Hence, as you see, we are practiced with every advises whichever mentioned in any forum. We have applied, but we don't see, it is coming to Crashlytics Dashboard even then.
Try below command. May be help full.
msbuild "/Users/xxx/projects/myApp/myApp/myApp.iOS/myApp.iOS.csproj" /t:"build" /p:Configuration="AppStore" /p:Platform="iPhone" /p:BuildIpa=true /p:FirebaseCrashlyticsUploadSymbolsEnabled=true
I have tried this command and it is working in my case. I get it from this git thread : https://github.com/xamarin/GoogleApisForiOSComponents/issues/386

Unity Android build crashes on start due Proguard

A development build works fine, but when I try a release build, it crashes immediately on start due to the Proguard.
I installed Crashlytics to try getting any error but it does not show any error (crashlytics works).
Might be important to add:
Just added Firebase and Facebook SDK.
How should the proguard.txt file look like?
Thank you in advance.

how to solve to build ionic 3 with firebase issue

ran build without fail yesterday but suddenly firebase issue has occurred. what should i set for this issue?
i tried the following
cordova.system.library.4=com.google.firebase:firebase-core:16.0.9
cordova.system.library.5=com.google.firebase:firebase-messaging:18.0.0
cordova.system.library.6=com.google.firebase:firebase-config:17.0.0
cordova.system.library.7=com.google.firebase:firebase-perf:17.0.2
link:
https://firebase.google.com/support/release-notes/android#update_-_may_31_2019
but that shows that
What went wrong:
The library com.google.firebase:firebase-iid is being requested by various other libraries at [[18.0.0,18.0.0]], but resolves to 19.0.0. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.
so i changed messaging version that
cordova.system.library.5=com.google.firebase:firebase-messaging:19.0.0
but also shows error
What went wrong:
Execution failed for task ':app:processDebugResources'.
Failed to execute aapt
ionic cordova build android
ionic cordova run android
I did what firebase shows me to do, but it hasn't been resolved.
thanks
Take a look at this thread: https://github.com/arnesson/cordova-plugin-firebase/issues/1081
In particular #dpa99c's comment
https://github.com/arnesson/cordova-plugin-firebase/issues/1081#issuecomment-503135862
I was having the same problem since the Firebase support update (June 17, 2019) but running through those steps in #dpa99c's comment worked for me.
In addition to this, if you are building for iOS as well then you may need to update to the latest version and install pod inside your iOS platform folder if you haven't done so already.

React-native-firebase error after first build

I am developing a cross platform application for Android and iOS and have chosen to use react-native-firebase. I have cloned the project from react-native-firebase free starter kit. When I build my application the first time using "npm run android" it works fine but the second time I get the error:
Execution failed for task ':app:processDebugGoogleServices'.
Failed to delete: C:\\android\app\build\generated\res\google-services\debug
To run the application again in the Android Studio emulator I have to manually delete the build folder and run "npm run android" again so it can create a new one. Why is this happening and how can I solve it?
I have the same problem.
Though, as a workaround, I don't clean the build folder : I start again the build (react-native run-android) and it goes live.
I may have to start several times.
So that means that the problem is about synchronization in the build process.
I've tried to set in my gradle.properties :
org.gradle.parallel=false
org.gradle.workers.max=1
Till now it works fine!

Resources