You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrade omise from 4.+ to version 5.4.0.
My Unit test failed
Logs
Java HotSpot(TM) 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
Task :app:testReleaseUnitTest FAILED
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/sam/.gradle/caches/transforms-4/142166b1a4c6acbf31ffeadb0fd0f22b/transformed/jetified-logback-android-1.3.0-3-runtime.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/sam/.gradle/caches/transforms-4/dddc98967a8d3dc98a00b6aa4bd4906f/transformed/jetified-logback-android-1.3.0-3/jars/classes.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
'boolean android.util.Log.isLoggable(java.lang.String, int)'
java.lang.UnsatisfiedLinkError: 'boolean android.util.Log.isLoggable(java.lang.String, int)'
at android.util.Log.isLoggable(Native Method)
at android.os.storage.StorageManager.(StorageManager.java:138)
at android.os.Environment$UserEnvironment.getExternalDirs(Environment.java:184)
at android.os.Environment.getExternalStorageState(Environment.java:1279)
at ch.qos.logback.core.android.AndroidContextUtil.getMountedExternalStorageDirectoryPath(Unknown Source)
at ch.qos.logback.core.android.AndroidContextUtil.setupProperties(Unknown Source)
at ch.qos.logback.classic.util.ContextInitializer.autoConfig(Unknown Source)
at org.slf4j.impl.StaticLoggerBinder.init(Unknown Source)
at org.slf4j.impl.StaticLoggerBinder.(Unknown Source)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Unknown Source)
at io.mockk.impl.log.JvmLogging.slf4jOrJulLogging(JvmLogging.kt:10)
at io.mockk.impl.JvmMockKGateway.(JvmMockKGateway.kt:166)
Screenshots
Name and version information
Android Studio Ladybug | 2024.2.1 Patch 1
Omise sdk version 5.4.0
The text was updated successfully, but these errors were encountered:
Hello @juckrit ,
Thank you for reaching out,
I believe that the error that you are facing is due to the fact that in our latest releases we added the library:
implementation "org.slf4j:slf4j-api:1.7.36"
And in your app it seems that you are using some other version.
Can you please refer to the guide indicated in your logs to help you resolve the issue: http://www.slf4j.org/codes.html#multiple_bindings
Thank you.
Expected behavior
Unit test should pass
Actual behavior
got Error
Steps to reproduce the issue
After upgrade omise from 4.+ to version 5.4.0.
My Unit test failed
Logs
Java HotSpot(TM) 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
'boolean android.util.Log.isLoggable(java.lang.String, int)'
java.lang.UnsatisfiedLinkError: 'boolean android.util.Log.isLoggable(java.lang.String, int)'
at android.util.Log.isLoggable(Native Method)
at android.os.storage.StorageManager.(StorageManager.java:138)
at android.os.Environment$UserEnvironment.getExternalDirs(Environment.java:184)
at android.os.Environment.getExternalStorageState(Environment.java:1279)
at ch.qos.logback.core.android.AndroidContextUtil.getMountedExternalStorageDirectoryPath(Unknown Source)
at ch.qos.logback.core.android.AndroidContextUtil.setupProperties(Unknown Source)
at ch.qos.logback.classic.util.ContextInitializer.autoConfig(Unknown Source)
at org.slf4j.impl.StaticLoggerBinder.init(Unknown Source)
at org.slf4j.impl.StaticLoggerBinder.(Unknown Source)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Unknown Source)
at io.mockk.impl.log.JvmLogging.slf4jOrJulLogging(JvmLogging.kt:10)
at io.mockk.impl.JvmMockKGateway.(JvmMockKGateway.kt:166)
Screenshots
Name and version information
Android Studio Ladybug | 2024.2.1 Patch 1
Omise sdk version 5.4.0
The text was updated successfully, but these errors were encountered: