Related
Anyone's snapchat forceclosing on android M? I just updated my snapchat and it opens and forecloses right away. Please help.
Just google snapchat apk and download a version that is 2 versions old.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------
http://www.apkmirror.com/apk/snapchat-inc/ version 9.9.0.0 works great
Sent from my Nexus 6 using Tapatalk
Missing Native Libraries
Hiya,
This is caused by the Snapchat APK not having the libscplugin.so and libsccrypto.so native libraries within the armeabi-v7a folder.
These are required in order for the application to sign the login requests.
I'm not sure why they haven't included them in that build, must be something to do with the Android M ABI configuration.
I extracted the libs from the APK downloaded from Google Play with Lollipop and then Android M.
The Lollipop APK has all of the required libs in armeabi-v7a folder, and does not include an x86 folder.
However, the Snapchat APK downloaded via Google Play on Android M contains an armeabi-v7a AND an x86 libs folder...
The issue here, is that in the APK for Android M, the libsccrypto.so and libscplugin.so do not exist.
This is what is causing the force crash when you press the login button.
No idea how long it will take Snapchat to fix this, but since this is a preview build of Android M, it could be an issue with Android M itself, not sending the correct device information to Google Play.
Cheers,
Liam Cottle
spartandawgs_03 said:
Anyone's snapchat forceclosing on android M? I just updated my snapchat and it opens and forecloses right away. Please help.
Click to expand...
Click to collapse
You kind of have to go with the expectation that some things just won't work right when running a preview
I was having the same problem, but the newest version of Snapchat (9.13.0.0) and the beta (9.13.2.0 beta) work fine on Android M Preview 2.
I have tries the latest beta. It doesn't seem to work for me. I've only been able to get 9.9.00 to work for me. What's your setup. I'm running stock preview 2.
I'm on stock m preview 2 latest beta works fine
Okay so I discovered that it won't let you log in on the latest but if you're already logged in then you can update the app and it should work.
So just download 9.9.00 and log in then update.
mrgoodpaul said:
Okay so I discovered that it won't let you log in on the latest but if you're already logged in then you can update the app and it should work.
So just download 9.9.00 and log in then update.
Click to expand...
Click to collapse
I did this on Preview 2 without realizing it and it worked, but then installed it from the Play Store after flashing Preview 3. I ran into the same problem on the new preview, but the same workaround solved it.
I just did a 100% fresh install of Android M-preview3, and here's the steps i took to get Snapchat working on my phone.
Downloaded Snapchat from the Play Store, v9.14.1.0
Tried to login; Force Close!
Uninstalled v9.14.1.0
Downloaded v9.9.0.0 from Apk Mirror
Installed v9.9.0.0
Tried logging into the app... Login successful!!!
Went to the Play Store and updated the app to v9.14.1.0
Ran the app... No force close!
pr0ndigy said:
I just did a 100% fresh install of Android M-preview3, and here's the steps i took to get Snapchat working on my phone.
Downloaded Snapchat from the Play Store, v9.14.1.0
Tried to login; Force Close!
Uninstalled v9.14.1.0
Downloaded v9.9.0.0 from Apk Mirror
Installed v9.9.0.0
Tried logging into the app... Login successful!!!
Went to the Play Store and updated the app to v9.14.1.0
Ran the app... No force close!
Click to expand...
Click to collapse
This worked, thanks!
How'd you manage to login? When I try to it says that version of Snapchat is no longer supported
tycemang said:
How'd you manage to login? When I try to it says that version of Snapchat is no longer supported
Click to expand...
Click to collapse
I've got the same problem, looks like Snapchat doesn't support the old versions anymore, so you are forced to update the app, but when you do it you can't log in because it crashes.. You have to wait until Snapchat fixes the bug. I am going back to Lollipop, can't live without Snapchat
tycemang said:
How'd you manage to login? When I try to it says that version of Snapchat is no longer supported
Click to expand...
Click to collapse
yes, this workaround doesn't work anymore
am I really going to go back to lollipop just bc of snapchat..?!
philsfan said:
yes, this workaround doesn't work anymore
am I really going to go back to lollipop just bc of snapchat..?!
Click to expand...
Click to collapse
I am, until Snapchat publishes an update or there is another solution, but I think that this workaround was the only one..
Has anyone else discovered a fix for this?
https://www.reddit.com/r/nexus6/comments/3jstwq/new_workaround_for_snapchat_on_android_m/
Here's a workaround. I haven't tried it yet.
Latest Snapchat update works for M!
No problems with Snapchat on m
Updated to the new version of snapchat and can finally log in on android m. I'm having issues with the new lenses feature and recording video snapchats. anyone else?
Hi can be people please tell me if the Barclays Mobile Banking works on their P9 and also what version of Android/Emui there using.
https://play.google.com/store/apps/details?id=com.barclays.android.barclaysmobilebanking
Thanks
bcartwright86 said:
Hi can be people please tell me if the Barclays Mobile Banking works on their P9 and also what version of Android/Emui there using.
https://play.google.com/store/apps/details?id=com.barclays.android.barclaysmobilebanking
Thanks
Click to expand...
Click to collapse
Working fine for me. I'm on L09C432B182
Apparently it isn't compatible with any Huawei handset that has been upgraded to EMUI 5.0.
I literally updated mine just the other day, and it just crashes out on starting up the app. . . frustrating.
I do hope they manage to fix it soon.
smithal_uk said:
Apparently it isn't compatible with any Huawei handset that has been upgraded to EMUI 5.0.
I literally updated mine just the other day, and it just crashes out on starting up the app. . . frustrating.
I do hope they manage to fix it soon.
Click to expand...
Click to collapse
yep mines the same wasn't sure if it was just my device
bcartwright86 said:
yep mines the same wasn't sure if it was just my device
Click to expand...
Click to collapse
Have you tried clearing the Apps Cache & Data. Maybe if you clear both and start the login process again, it will work?:fingers-crossed:
tmohammad said:
Have you tried clearing the Apps Cache & Data. Maybe if you clear both and start the login process again, it will work?:fingers-crossed:
Click to expand...
Click to collapse
As said above works on marshmallow but not on Nougat.
I've spoke to Barclays they are aware of the problem didn't give me a time frame for when the app would work just check when the app updates
Well, at least it's not just me. My phone only recently updated to EMUI 5.0 (Nougat) build and suddenly, Barclays is dead. Great.
Same problem here. On the Honor 6x, EMUI 5.0.
yes known problem barclays are aware. i rolled back to MM so I could use this app mainly.
Did you guys read the changelog before updating to Android 7? It specifically says that the Barclays app would crash because it doesn't support Android 7.
jonezie said:
Did you guys read the changelog before updating to Android 7? It specifically says that the Barclays app would crash because it doesn't support Android 7.
Click to expand...
Click to collapse
And working on 7.1/7.1.1? Just because working fine on all my devices running those versions of N, but the Huawei.
thefiqs said:
And working on 7.1/7.1.1? Just because working fine on all my devices running those versions of N, but the Huawei.
Click to expand...
Click to collapse
Try updating it on playstore. This might solve the issue.
Received an update today which fixed the app (for the Honor 6x at least).
Still not working on P10 or Pingit!!!
Barclays need to sort this!!
working on my p9 EVA-L09C432B386
is it now working for you guys?
this looks much like what i'm experiencing on Moto Z2 Play since I got the device....
same story all over again....
hi
Barclays app after last update not working on my xiaomi mi5 lineage 7.1.2
I solved the installation by version before last update. Version 1.42 works with me no problem.
Source
Code:
apkmonk
I can't give you link (posts limit)
I checked the play protect so it is probably ok.
Hello guys,
Am I the only one having issues with the latest facebook messenger update ?
It keeps crashing on me when I enter the app or when I'm writing a message ...
It's the Messenger fault, it's crashing for me too since at least few updates; I'm on self-compiled ArrowOS (but planning to change)
przemcio510 said:
It's the Messenger fault, it's crashing for me too since at least few updates; I'm on self-compiled ArrowOS (but planning to change)
Click to expand...
Click to collapse
Aha ! I couldn't find any thread anywhere, I thought I was the only one having these issues !
I rolled back on an older version, no more crashes, but now everytime I enter a chat, my phone plays a messenger notification as if I had received a new message... What the hell is going on at FB headquarters
Had same issue at 5.0.6
Latest messenger beta works great though.
com.facebook.orca_192.0.0.19.101-130757045_minAPI21(armeabi-v7a)(280,360,400,420,480,560,640dpi)_apkmirror.com
Sent from my ONEPLUS A3003 using Tapatalk
Hi. I have the same problem, it crashes when I'm typing. I'm rooted, I have magisk and Xposed. Need some help
Cajmonet said:
Hi. I have the same problem, it crashes when I'm typing. I'm rooted, I have magisk and Xposed. Need some help
Click to expand...
Click to collapse
Beta version of Messenger works fine
przemcio510 said:
Beta version of Messenger works fine
Click to expand...
Click to collapse
I uninstalled and downloaded an old version instead, works fine now.
If not mistaken, messenger crash is because of xposed.
Same problem with me too, NLOS, Magisk and Xposed. I'm now using Messanger lite without any crashes.
oos 5.0.7 and Xposed and magisk
Messenger lite works fine on my oneplus 3t
OxygenOS Open Beta 17 (OnePlus 7 Pro)
Changelog:
System
Newly added user assistance feature to help user master usage skills quickly(Route: Settings>OnePlus Tips&Help)
Fixed the abnormal error occured in Lockbox
Fixed the auto-start issue with QXDM logs after reboot
Optimized user experience with long screenshot in some scenarios
Updated Android security patch to 2020.08
Messages
Optimized the categorization, messages of the same contact now merged in one card（India only）
File Manager
Fixed the issue that File Manager did not display some downloaded documents of apps
Network
Improved the stability of Wi-Fi transfers
OxygenOS Open Beta 17 (OnePlus 7 Pro)
2.2 GB official download link:
https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus7ProOxygen/OnePlus7ProOxygen_13.W.41_GLO_041_2007291643/OnePlus7ProOxygen_13.W.41_OTA_041_all_2007291643_5f80f3e.zip
Local Upgrade OnePlus 7 Pro
1.) Download zip file OxygenOS Open Beta 17 2.2 GB from Official server
and copy it to the root of the internal memory
(i.e., not in a folder such as Downloads, for example).
2.) Go to Settings> System> System Updates> Click the gear at the top right>
Local Upgrade> Click on the appropriate installation package> Update
3.) After the update is completed, click Restart
4.) The update was successful.
Note If you do not see the firmware file, then check the file extension should be .zip
(if you have .zip.jar just rename it by deleting .jar)
Who already updated?
Who already updated? Is it safe to do so? No being locked out of device or something? ?
KennethHau said:
Who already updated? Is it safe to do so? No being locked out of device or something?
Click to expand...
Click to collapse
If you have OnePlus 7 Pro
and you want to install OxygenOS Beta 17
-----------------------------------------------------
This is the official Beta version.
It is installed and used without any problems.
KennethHau said:
Who already updated? Is it safe to do so? No being locked out of device or something? ?
Click to expand...
Click to collapse
Just done no issue
Sent from my OnePlus7Pro using XDA Labs
Thanks! Updated too and all is fine
Any news about one handed mode in this build?
Sent from my GM1913 using Tapatalk
sudanking said:
Any news about one handed mode in this build?
Sent from my GM1913 using Tapatalk
Click to expand...
Click to collapse
Nope..it's not available.
No buds compatibility included. Can someone pull the buds APK from the stable and upload it?
This changelog is lame, time for 11 beta already
Google Pay broken?
Is anyone else having issues with Google Pay?
I'm getting an error saying that the device is rooted or running an uncertified software.
EDIT: looks like SafetyNet is failing.
W.
maddler said:
Is anyone else having issues with Google Pay?
I'm getting an error saying that the device is rooted or running an uncertified software.
EDIT: looks like SafetyNet is failing.
W.
Click to expand...
Click to collapse
I am on OB17 and Safety Net passed. I don't use Google Pay so I cannot comment. I am stock, no root.
I am having bootloop issue on oneplus7pro with OOS openbeta 17 after flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip,it was working on openbeta16,anyone here facing the same issue?
Did someone update with Magisk and system update yet (using TWRP Retention.zip)?
My phone is rooted and I have a custom kernel installed, is it safe to update?
I'm having bootloop on ob17 using latest twrp and magisk canary, modules disabled, stock kernel. Boots fine if magisk is uninstalled.
die_braut said:
Did someone update with Magisk and system update yet (using TWRP Retention.zip)?
Click to expand...
Click to collapse
yes and no problems
FlipmodeBG said:
I'm having bootloop on ob17 using latest twrp and magisk canary, modules disabled, stock kernel. Boots fine if magisk is uninstalled.
Click to expand...
Click to collapse
No issues here. Did not use TWRP retention, just flashed installer.
omar302 said:
I am on OB17 and Safety Net passed. I don't use Google Pay so I cannot comment. I am stock, no root.
Click to expand...
Click to collapse
The only other thing that changed recently is an update to Google Play Services (beta).
Can you confirm which version you've got there?
EDIT: ignore, downgraded Google Play Services to latest stable version and still failing.
Not sure what went wrong, but I guess the only solution is a factory reset at this point
Thanks!
W.
@Oswald Boelcke @Funk Wizard
I'm new on op7/p forums but I'm coming from op5 and they have dedicated pinned threads for all OB/Stable builds instead individual ones for each new build.
Is possible to have this? Is there any volunteer?
Enviado desde mi GM1917 mediante Tapatalk
Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible.
Finding out what exactly is causing the root detection is beyond my technical abilities but I would provide as much information needed to those willing to help.
---
Update: December 14th 2021 - Method no longer sufficient
---
The solution found by @pxrave appears to be working:
pxrave said:
Hey fellas I got it working and others apps detect magisk before.
Update to latest v23
Install modules riru and riru unshare
Remove data from tan app
Go to magisk hide and tick all process to hide included the isolated
Start the tan app and do the activation again.
Problem you need wait 2 days to activate because comdirect use new activation process for photo tan app.
Working fine all version 8.3
Click to expand...
Click to collapse
Link to the Riru Unshare module:
GitHub - vvb2060/riru-unshare
Contribute to vvb2060/riru-unshare development by creating an account on GitHub.
github.com
also stcpay yesterday is updated to 1.6 and started to detect my magisk canary (22105)
I can confirm what swour says.
on Android 9 and 11, my magisk root is recognized, magiskhide is active and the phototan app is added.
Yes this is a serious problem. I used xposed magisk and x privacy... Latest comdirect tan app detect all...
+1
+1 big issue for me
Only solution I found (for now): Go back to version 8.2.1 using a backup or any mirror, e.g. https://downloadapk.net/comdirect-photoTAN-App.html
Unfortunately you need to register again then
I have already applied the update. The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem. I have an absolutly clean Android 8.1 build on the phone for banking. It's crazy that the bank is make it so difficult for us to use a save own build.
allrightlite said:
The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem.
Click to expand...
Click to collapse
Perhaps that is too optimistic. I doubt that one app is of great interest
Asellus said:
one app is of great interest
Click to expand...
Click to collapse
Until the new root detection is also available for other apps, it will be fixed quickly.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Thanks, then I will easly wait. No need to reactivate hopefully.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Asellus said:
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Click to expand...
Click to collapse
I don't think so, there is at least one other app that shows the same behavior.
new root dedction
i updated stc pay yesterday to 1.6 and it found my magisk canary (22105) the think i notes is the (isolated) is added to the app !!!
forum.xda-developers.com
I also noticed the (isolated) thing with me.
I tried with v23 this morning, w/o success :-(
Same here, got v23 and working safetynet-fix, no success. Downgraded photoTAN to v8.2.1 .
+1
I'm not surprised, there is nothing in the changelog that this has been fixed.
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I have a ZTE Blade L130 with the old photo tan app, that is my rescue. But you can't activate the old one. But it's keep working.
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I had to unhide the app in magisk hide and hide it again, after that it worked.