Twilio: Android Error TwilioConversations [Signaling] - java

I have a problem when call ends, and finish() to current activity of conversation, app blows me, but does not show me any error, and often appears me this error:
E/TwilioConversations: [Signaling]:RESIP::TRANSPORT: Got TLS read ret=0 error=6 error:00000006:invalid library (0):OPENSSL_internal:public key routines
If someone could help me because I have a lot of time with this problem.

Do you have other 3rd-party libraries that use SSL? There may be a conflict between the Twilio Video SDK and another library.
I have also seen this resolved by ensuring that you have the latest version of the SDK installed.
However, if you can let me know any more specifics regarding your code, I'm happy to help debug further.

Related

Does the java version make any difference when building a Flutter app?

I am wandering if building a Flutter app with different java versions make any difference. Could the version influence if the app crashes or not in an old device, for example?
Generally, It won't effect anything. However, if you're using some plugin/package that require specific java version, it might cause a problem. If your app crashes, read the log and see if it is caused by a package/plugin and if so, that particular package might need a specific version.

java.lang.VerifyError in android api < 21(KitKat)

I am facing this issue when am trying to open my app below the lollipop version of Android, am really stuck with this issue. so kindly help me out from this issue Thanks in advance
You need to look at Log and see what's causing the VerifyError. The cause is probably there is some method in a java.lang class that is not supported on the android SDK level you are using.

Really Odd Android App Update Bug

I previously had an android app released on Google Play. I pushed out another update a couple days ago, but about 80% of the time, when a user tries to update to the new version, it seems to download and install the app correctly, but then displays a blank screen on startup. This issue doesn't go away until they either restart their phone, or do a full uninstall and reinstall of the app.
I've tried googling around for answers, but it is hard to describe the problem so I haven't found anything.
If anyone has any ideas as to why this might happen I would be really grateful.
Thanks!
It could be a number of things depending on what changed in your update. Has anyone posted any sort of log, or did it happen on your device for you to log? Since it isn't happening on everyone's device it is going to be a tough call just from my minimal experience. Is it possible that the 20% of the people not having the issue had a later version than the one just before your last patch or does your app require an up-to-date version to run (for example they updated from 1.1 to your newest 1.5 instead of from 1.4 to 1.5)? Like I say, may be easier to help with if you can let us know more specifically what was changed.

Reasons an app could work on android 2.3 and fail on android 3.0

I have written an app that appears to work faultlessly on android 2.3. I have just been told by email that my app crashes (immediately on startup) on android 3.0 tablets. Unfortunately I do not have access to such a device.
To try and make my app as crashproof as possible I have been employing Lint and FindBugs. My program does use more than one thread and Findbug reports several instance of "Inconsistent synchronization" because different threads may be reading certain data at the same time. I beleive this not to be a problem because at the times the data is being read it should not be in the process of being altered. It occurs to me though that perhaps android 3.0 has some built-in detection of such instances?
I am interested in any other thoughts on what kind of things would cause a program to work on 2.3 but not on 3.0.
I had a similar problem with an app.
My issue was due to the introduction of a new exception when I attempt to perform a networking operation on the main UI thread.
Please refer to How to fix android.os.NetworkOnMainThreadException? to have more explanation.
I also used the Android emulator with the Android 3.0 API to reproduce the bug.

phonegap 1.0 android facebook plugin login fail

i'm adding facebook post button to my app (phonegap 1.0), it seems that the only method to have this working is using the plugin here:
https://github.com/jos3000/phonegap-plugins/tree/master/Android/Facebook
But it's not working for me, first i saw in the log PluginManager not found, reading the docs it seems plugins are not being loaded like that anymore.
But the intent and dialog of facebook appear when calling
window.plugins.facebook.authorize(appID, function(res){...})
I can see the facebook page being loaded but just after it finished the page automatically goes back with no response.
Anyboy has used succesfully this plugin??. actually the whole phonegap-plugin system seems to be very buggy... but i can't change the framework right now all the rest of the app is working.
At the end i managed to have it working by changing the Facebook authentication option in the java file, not using single sign on.
By the way i do NOT recommend phonegap... it seems to me the library is still full of bugs
I've only ever had very minor issues working with PhoneGap and iOS. Most we were able to find quick workarounds to resolve.
The issue is Android itself. I'm trying to avoid supporting it until Google steps in and enforces standards on every phone device manufacturer. Otherwise, you're guaranteeing yourself a swiss cheese codebase to deal with workarounds on every single device out there.

Categories