My issue is that I used the LeakCanary library in android. com.squareup.leakcanary:leakcanary-android:2.9.1, here my code runs and works successfully in debug mode, but when I create a release, then get an error like this.
package leakcanary does not exist
import leakcanary.AppWatcher;
^
anyone have solution for this error
Related
I am getting this error:
Failed building JavaScript bundle. Unable to resolve
“expo-app-loading” from “App.js”
when I ran my project after a couple of months. Earlier it was working fine but not now.
Can someone please help me out?
If you recently updated SDK versions (expo upgrade), please be sure to review the breaking changes carefully as is advised when you complete the install.
For instance, SDK-40 which was released in December has breaking changes notes about expo-app-loading that probably addresses what you're seeing perfectly.
Read this page : https://blog.expo.io/expo-sdk-40-is-now-available-d4d73e67da33
Look for section title: AppLoading has been extracted from the expo package
There were two problems:
expo-app-loading was not in my package.json, so I just installed it again and boom, it was in my packege.json then.
I was importing 'AppLoading' the wrong way. I wrote
import {AppLoading} from "expo-app-loading"; //wrong way
Which was breaking. Then I corrected it to
import AppLoading from "expo-app-loading"; //correct way
Which solved the issue.
I have implemented Capacitor plugin for Firebase Crashlytics in my Ionic 5 app following this doc. I completed all the steps but getting the following error.
error: package com.getcapacitor.community.firebasecrashlytic does not exist
^
This error is coming when Android Studio is trying to build the project. The error is comming the the MainActivity.java class in line import com.getcapacitor.community.firebasecrashlytic.FirebaseCrashlytics;
In short
There is a typo in README. I managed to fix it by adding s in firebasecrashlytic.
Just change import com.getcapacitor.community.firebasecrashlytic.FirebaseCrashlytics; to import com.getcapacitor.community.firebasecrashlytics.FirebaseCrashlytics;
Some fun
There was an issue related to this "bug". The issue was closed without fixing the cause.
There are already a few pull requests (like this one) waiting for approval.
I'm new on react, and i tried to run my app but i got this following error
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.bits.bee.bwc, PID: 12601
java.lang.AssertionError: APK bundle must contain the expected embedded asset asset_c2f3d742a18a28238b7cd34a5d4b7316.png
at expo.modules.updates.loader.EmbeddedLoader.copyAllAssets(EmbeddedLoader.java:174)
at expo.modules.updates.loader.EmbeddedLoader.processManifest(EmbeddedLoader.java:137)
at expo.modules.updates.loader.EmbeddedLoader.loadEmbeddedUpdate(EmbeddedLoader.java:57)
at expo.modules.updates.UpdatesController.start(UpdatesController.java:286)
at expo.modules.updates.UpdatesController.initialize(UpdatesController.java:96)
at com.bits.bee.bwc.MainApplication.onCreate(MainApplication.java:98)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1011)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4552)
at android.app.ActivityThread.access$1500(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1342)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5255)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:652)
Can someone explain to me how it's work because i looked it up in my asset folder there's nothing named like that. And how do i fix this? Thanks
Info
This exception only happened to me when running a debug build with react-native run-android and the exception did not appear when running a release build with react-native run-android --variant=release.
Solution
Check whether you have the following line in MainApplication.java and if it's there then remove that line:
import com.facebook.react.BuildConfig;
Explanation
The line import com.facebook.react.BuildConfig; causes UpdatesController.initialize(this); to be called in Debug mode which shouldn't happen.
More detail:
When you look at your Stacktrace you posted the line
at com.bits.bee.bwc.MainApplication.onCreate(MainApplication.java:98)
points to UpdatesController.initialize(this);. Including the line above and below that's how it looks like:
if (!BuildConfig.DEBUG) {
UpdatesController.initialize(this);
}
This BuildConfig here points to the BuildConfig class of your package (com.bits.bee.bwc in your case) which is created during the build. If you import com.facebook.react.BuildConfig it will point to another BuildConfig class which does not contain the correct DEBUG value you want.
Since BuildConfig.DEBUG will then be undefined or false, UpdatesController.initialize(this); is called although it shouldn't during a debug build. Hence, because assets will be not embedded for debug builds, the copyAllAssets function which is eventually called will not find any assets and we get the above error.
Some Context of why I ended up importing com.facebook.react.BuildConfig;
I was facing the issue of java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so in my release build and followed the advice to add that line as stated here https://stackoverflow.com/questions/57036317/react-native-java-lang-unsatisfiedlinkerror-couldnt-find-dso-to-load-libherm/63048532#answer-62119615. It didn't make a change for the release build and I forgot about it. Only later when I attempted to make a debug build I got this error.. took me quite a while to realize that this added line is the cause of the issue!
What I learned from debugging this issue:
Don't just add things because you think it won't hurt. If it doesn't fulfill a certain purpose or has no effect, remove the change immediately. It can otherwise cause strange side effects later.
If you have build issues with Android, debug with Android Studio instead of Flipper. Flipper doesn't display you the entire Stacktrace and in Android Studio you can easily browse through all the Java files which eventually helped me to understand this Exception.
I have tested my app on many devices and everything goes well but when I'm trying to generate a signed apk this message appears: Expected resource of type interpolator [ResourceType]
This line seems the problem:
scaleDown.setInterpolator(AnimationUtils.loadInterpolator(activity, android.R.anim.decelerate_interpolator));
Behind this line there is a class called AnimationUtils, this class belongs to android SDK so I don't understand why when I inspect its the source code the following imports show me Cannot resolve symbol
import android.annotation.AnimRes;
import android.annotation.InterpolatorRes;
I already tried clean and rebuild.
I finally overcome this issue replacing
AnimationUtils.loadInterpolator(activity, android.R.anim.decelerate_interpolator)
To this
new DecelerateInterpolator()
1.try to change android.R.anim.a to R.interpolater.b
I just tried to Import the GreenDroid-Librarys for my new Android Application.
Now, I encounter a confusing Error. I first Import the GreenDroid-Core Library and everything is fine.
But when I, after that, try to Import the GreenDroid-GoogleAPI Library into my workspace I get a java.lang.StackOverflowError.
The detailed Error is as followed:
Failed to call IProjectListener.projectOpened
java.lang.StackOverflowError
I´m not sure if this is a problem with my Eclipse or with the Library per se.