ezeeworld / b4s-android-sdk Goto Github PK

Hi,

We have just published an update of our app, that integrates B4S SDK 1.8.4.
In our app, we use "Crashlytics" to obtain user crashs.
In one day, an user meet a same crash 25 times.

Trace :
Fatal Exception: java.lang.SecurityException: Unable to start service Intent { act=com.ezeeworld.b4s.android.sdk.monitor.B4S_QUERY_VERSION cmp=com.ezeeworld.qelmc/com.ezeeworld.b4s.android.sdk.monitor.MonitoringManager (has extras) }: Unable to launch app com.ezeeworld.qelmc/10145 for service Intent { act=com.ezeeworld.b4s.android.sdk.monitor.B4S_QUERY_VERSION cmp=com.ezeeworld.qelmc/com.ezeeworld.b4s.android.sdk.monitor.MonitoringManager }: com.ezeeworld.qelmc is restricted
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1760)
at android.app.ContextImpl.startService(ContextImpl.java:1733)
at android.content.ContextWrapper.startService(ContextWrapper.java:515)
at com.ezeeworld.b4s.android.sdk.monitor.MonitoringManager.onHandleIntent(SourceFile:120)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
NB : Line numbers could be not the good ones

This user have got a TCL 604yL device (Alcatel one Touch 3.2.5 LTE) with android 5.0.2.
His phone is not rooted.
That sounds be a device's blocking. Perhaps the user have an anti-virus.

Could you add a fix or catch the problem to avoid a crash ?

Best regards,
Gaël

Bonjour,

Depuis que nous avons intégré votre SDK (version 1.8.4), nous avons des remontées de crash de notre application, dû à un excès de threads existants à un instant t. Cela entraîne un OutOfMemoryError. CE crash peut même survenir quand l'application est arrêtée. Dans les traces d'erreurs, nous voyons qu'il y a énormément de threads créés par votre SDK (> 900 threads).
Je pense qu'il doit avoir un problème de threads à durée infinie.

Trace du crash :
Fatal Exception: java.lang.OutOfMemoryError: pthread_create (stack size 16384 bytes) failed: Try again
at java.lang.VMThread.create(VMThread.java)
at java.lang.Thread.start(Thread.java:1029)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:920)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1338)
at de.greenrobot.event.util.AsyncExecutor.execute(SourceFile:111)
at com.ezeeworld.b4s.android.sdk.monitor.InteractionService.onStartCommand(SourceFile:122)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2845)
at android.app.ActivityThread.access$2100(ActivityThread.java:164)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1355)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:157)
at android.app.ActivityThread.main(ActivityThread.java:5350)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)
at dalvik.system.NativeStart.main(NativeStart.java)

La trace des threads actifs est la suivante :
pool-14-thread-695
at com.ezeeworld.b4s.android.sdk.monitor.e.a(SourceFile:89)
at com.ezeeworld.b4s.android.sdk.monitor.InteractionService$4.run(SourceFile:129)
at de.greenrobot.event.util.AsyncExecutor$1.run(SourceFile:115)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

Cordialement,
Gaël

Hi,

I've noticed that in the latest release, the most recent play services you're supporting are 9.2.1. Would it be possible to get support for more recent versions like 9.8+ ?

Thanks in advance

Bonjour,

Nous rencontrons un problème de performances dans notre application lié à B4S.
Pour information, notre application permet de télécharger des fichiers assez volumineux (50 Mo) dans un thread, qui n'est pas le principal.
Sur certains appareils (dont le Nexus 9), lorsque B4S est intégré et que le bluetooth est activé, le téléchargement devient extrêmement lent.
Sur le même appareil, sans le SDK B4S et avec le bluetooth activé, la vitesse du téléchargement est normal.
Sur le même appareil, avec le SDK B4S et avec le bluetooth désactivé, la vitesse du téléchargement est normal.
Sur d'autres appareils (Galaxy tab 4 7 pouces), nous n'avons pas ce comportement.

Avez-vous une idée du problème ? Contrôleur Wifi/Bluetooth saturé ?
Pouvons-nous régler la fréquence des scans bluetooth ?

NB : Nous avons plusieurs clients qui se plaignent de problèmes de téléchargement depuis la sortie de notre application avec le SDK B4S.

Cordialement,
Gaël

Hi,
Just trying to launch the "sample" app and it crashes telling it can't find the InteractionHandler class.

Hi,
I want to add the B4S Gradle dependency to my project.
However my project is set with Retrofit 1.9 instead of 2.0.0-beta2.
It generated an exception : java.lang.NoClassDefFoundError: retrofit.Retrofit$Builder

My question is, is it possible to use your SDK with retrofit 1.9?
If so, what must be configured?

Thank you by advance
Best regards

Hi,

I'm trying to integrate your SDK (1.7.3 version) with Android Studio. Your SDK manifest declares minSDK to API Level 18. Our application have got a min SDK of 15. To use your SDK without changing our application compatiblities, we must use a tools:overridding for minSDK.
Of course, we don't initialize SDK or call it, if the APi Level of the device are lower than 18.
I did some quicks tests and that's seems to works (ie : no crash).
But I want to be sure, no background code can happen with device with old API Level and induce crashes.

Best Regatds,
Gaêl

Hi,

I am trying to integrate your SDK. I would like to know the proguard configuration of your SDK. Indeed, your SDK compile fine in debug, but not in release. Our project activate proguard in release mode. So I need to configure the proguard's project to keep the necessary elements of your SDK and third libraries.

Best regards,
Gaël

Bonjour,

Lors de la récupération par le SDK B4S de certaines informations de l'utilisateur, la méthode getAppInfo plante systématiquement sur certains appareils. En effet, le nom de l'appareil peut contenir des caractères spéciaux.
Appareil concerné : "ezee’tab10q14_l"

Trace :
Fatal Exception: java.lang.IllegalArgumentException: Unexpected char 0x2019 at 23 in header value: Android;4.4.2;alps eZee’tab10Q14-L;fr.package1.package2;3.5.0;1.8.4-master
at okhttp3.Headers$Builder.checkNameAndValue(SourceFile:283)
at okhttp3.Headers$Builder.add(SourceFile:233)
at okhttp3.Request$Builder.addHeader(SourceFile:177)
at com.ezeeworld.b4s.android.sdk.server.Api2$1.intercept(SourceFile:82)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(SourceFile:188)
at okhttp3.RealCall.getResponseWithInterceptorChain(SourceFile:161)
at okhttp3.RealCall.execute(SourceFile:57)
at retrofit2.OkHttpCall.execute(SourceFile:118)
at retrofit2.ExecutorCallAdapterFactory$ExecutorCallbackCall.execute(SourceFile:86)
at com.ezeeworld.b4s.android.sdk.server.InteractionsApi.getAppInfo(SourceFile:148)
at com.ezeeworld.b4s.android.sdk.monitor.ScanService$b.run(SourceFile:148)

Hello,

I'm trying to setup the SDK for android in order to detect one beacon to send a push notification.

I synchronized my beacon and created a campaign (simple push, from 0 to 1 meter, everyday).
I set up the android sdk and I deployed it on my nexus 5.
Everything seems to work well but when I move my beacon by the phone, it never detects or print or send anything.
What am I suppose to expect ? What did I miss ?

Thanks a lot :)

Julian

Hi,

Since I have integrated B4S SDK in our application, my phone informs me that my app consumes too much energy, even if Bluetooth is disabled.
In app log, I have noticed that the ScanService is always turned on. This log happens repeatedly when Bluetooth is disabled : "E/B4S: ScanService: Bluetooth is not enabled by the user: NO scanning can be performed right now (will try again next time)".
Is it possible to modify your SDK to turn off your service when the Bluetooth is not enabled ?
I think you can relaunch it when Bluetooth become enabled with a receiver on Bluetooth state changed event.

Best regards,
Gaël