Java lang error xiaomi

Xiaomi crash java.lang.SecurityException SYSTEM_ALERT_WINDOW #505

Crash on myMethodWithPermissionCheck() when use @NeedsPermission(Manifest.permission.SYSTEM_ALERT_WINDOW)

Library version : 3.3.1 with kapt processor
Devices affected : Only Xiaomi Mi A1
Stacktrace:

The text was updated successfully, but these errors were encountered:

Seems Xiaomi doesn’t support SYSTEM_ALERT_WINDOW ? 🤔

@francescobonni if you don’t use the library can you deal with the problem? 👀 (thank you for your report and sorry for being late 🙇 )

No problem, I’m trying to find a Xiaomi MI A1 to perform the test without using the library and check if the problem is in the library or device. I will give you updates on the problem as soon as possible

@francescobonni any update? 🙇

@hotchemi I’m sorry I had a lot of problems, but I found the device, this weekend I send you updates.

@hotchemi
Finally I have updates, I tested with a clean application, the system overlay request and I found the behavior to replicate the crash on xiaomi mi a1 (now on Fabric i see same crash with redmi note 4 and android 6).
The crash occurs only if you use the library, step to reproduce the crash:

1. Activate the permission for the overlay through the app
2. I open the app information (eg through the launcher) and revoke the permission for the overlay
3. Return to the app and try to activate the permission again
4. Crash
5. Reopen app and retry to activate permission
6. Crash
7. Close app from recent
8. Open and retry to activate permission
9. Crash
10. I install the same app with manual permissions, everything works
11. I try in my Nexus 6P, everything works, both permission dispatcher and manual permissions

If you want I can put on my github the sample project I used, but it’s very simple, a button that requires overlay permissions

@francescobonni oh it’s happening on Android 6 as well..could you give us your sample project if possible? 🙇 Weird.. 👁

I’m new on github, I did not know how to do things correctly, in the project at the moment you find 2 branches in addition to master (the first for the test without using the library and the second to test the library)

@francescobonni Thank you!

Device afflicted update:

• Xiaomi Mi A1 (Android 8.1 & Android 8.0)
• Xiaomi Mi A2 Lite (Android 8.1)
• Xiaomi Redmi Note 4 (Android 6)

Sorry for the late. I think the cause is in

if ( Build . VERSION . SDK_INT >= Build . VERSION_CODES . M && «Xiaomi» . equalsIgnoreCase ( Build . MANUFACTURER )) <

May be we don’t need to have a workaround for SYSTEM_ALERT_WINDOW 🤔

@francescobonni Do you think the same thing would happen with WRITE_SETTINGS ? 👀

@hotchemi this weekend I’ll try the WRITE_SETTINGS and update you

I guess you never tried it that weekend

Yes, I’m so sorry, but today I tried the write settings, same problem

ooh thank you. I’ll address.

Let us know your opinion #544

Since we’ve already removed Xiaomi support from the lib let us close the issue.
@francescobonni thank you for your dedicated contribution 🙇

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain] libunity.0007f0c0 #818

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2019.2.21f
• Firebase Unity SDK version: 6.15.2
• Source you installed the SDK: Unity Package Manager
• Problematic Firebase Component: Crashlytics
• Other Firebase Components in use: Messaging, Analytics, Dynamic Links
• Additional SDKs you are using: Facebook, MoPub
• Platform you are using the Unity editor on: Mac
• Platform you are targeting: iOS, Android
• Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:

Recently we updated Firebase SDK for unity to 6.15.2. Since the SDK update, getting this crashes reported on Firebase console for Android for armv7 devices.

Logs as per Firebase console:

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
We are not able to reproduce the crash

The text was updated successfully, but these errors were encountered:

With this limited information, we cannot determine whether if this is related to Crashlytics or even Firebase SDK.
Are you able to reproduce this crash using your app on a local device and captures more information from the log?
We also released 6.16.0 which actually resolves many Android build issues related to Crashlytics. Should be worth a try and see if that resolve your issue. Though most of those are for Unity 2020. Also be aware of the duplicated package name issue described here. #806

Otherwise, it would hard for us to take any action about your issue.

Hope this helps!
Shawn

Hey @gaurangtalwadkar. We need more information to resolve this issue but there hasn’t been an update in 5 weekdays. I’m marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

@chkuang-g
We updated to 6.16.0 but still getting the crash. We were able to reproduce the crash.
Steps to Reproduce:

1. Launch the app
2. Put app in background once initialisations complete
3. Use some heavy memory hogging apps.
4. Open app through push notification.

Источник

Игра Unity начала вылетать на android 8

Получил следующую трассировку стека от Android Vitals:

Понятия не имею. Любая помощь или объяснение будут приветствоваться.

Вероятно, ошибка. Обновите Unity до версии 2017.2. Может, починили.

Сегодня для нашего проекта в Android Vitals для пользователей на Android 8.0 и 8.1 начал отображаться такой же сбой. Мы используем Unity 2017.1.3. Возможно, это не зависит от версии Unity. Я обнаружил некоторую корреляцию возникновения такого сбоя с выпуском обновлений для Google Play Market.

Обновлено: Нам удалось воспроизвести эту ошибку на нашем устройстве Android 8.1:

• Запустить приложение на устройстве.
• Заставить Google Play Market остановиться.
• Попробуйте приобрести IAP в магазине.
• Просмотрите указанный отчет об ошибке в Android Vitals

Учитывая особенность этой ошибки, которая возникает неожиданно и массово, а затем также неожиданно полностью исчезает без внесения изменений в приложение, мы пришли к выводу, что системная служба останавливается принудительно при обновлении фона Google Play Market для пользователей с включенным автообновлением. и подключение к сети Wi-Fi во время использования нашего приложения, а затем попытаться получить доступ к данным или выполнить операцию с IAP в магазине Google Play.

Мы видим то же самое, Android 8, в основном устройства Samsung

Вы можете попытаться перехватить эту ошибку, попытаться повторно подключиться к службе и снова выполнить тот же IAP.

Мы наблюдали ту же ошибку на большой части нашей базы игроков. Мы смогли связаться с Unity и разобраться в ошибке.

Из службы поддержки Unity Enterprise:

We are aware of the issue. We fixed it in 2017.3 after upgrading the JNIbridge to support Oreo APIs. Previous reports describe that when a Unity application that has INTERNET permission is running, and the Google play services is updated, stopped or reboot, it will cause the app to crash in Android 8, 8.1 devices.

The problem is that ServiceConnection.onBindingDied which was added in API level 26 is not implemented before 2017.3; we added this for GoogleAdsServiceConnection in such version an also updated the JNIbridge to solve the problem.

I’m able to reproduce it in an empty project by setting Internet Access to «Require» and when running on the device, go to settings ->Apps & notifications->google play services->storage->MANAGE SPACE->CLEAR ALL DATA, then the app crashes as described in Stack Overflow.

Do you have plans to upgrade your project to 2017.4 LTS?

I’m asking because we think that a backport of the fix is not feasible, not only because it would be for a version for which we no longer create patches (5.6.x) but an appropriate fix would involve backporting the full support for Oreo APIs which might be tricky and may cause regressions.

Мы решили попробовать обновить нашу версию Unity с 5.6.4f1 до рекомендованных версий 2017 года. Похоже, это должно решить наши проблемы.

Источник

java.lang.Error: FATAL EXCEPTION Caused by com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator #974

Unity 2019.1.11 (same for 2019.1.10)
Google Ads SDK: 3.18.1 (same for 3.17)

My app is seeing a lot of these crashes:

java.lang.Error: FATAL EXCEPTION [main] Unity version : 2019.1.11f1 Device model : SPA Condor Electronics Plume P8 Pro Device fingerprint: Condor/Plume_P8_Pro/Plume_P8_Pro:7.0/NRD90M/1506402354:user/release-keys Caused by at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method) at com.unity3d.player.UnityPlayer.resume (Unknown Source) at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source) at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1269) at android.app.Activity.performResume (Activity.java:6775) at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3487) at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3556) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1587) at android.os.Handler.dispatchMessage (Handler.java:110) at android.os.Looper.loop (Looper.java:203) at android.app.ActivityThread.main (ActivityThread.java:6269) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1063) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:924)

I know these errors do not seem to be related to Google Ads, but please see this Unity Forum thread.

I also believe this is caused by Google Ads SDK. The numbers of errors is very high, reaching the Google Play bad behavior threshold. Please fix!

The text was updated successfully, but these errors were encountered:

Источник

Вернуться в Общие вопросы

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 8



в манифесте прописано следующее:
<uses-permission android:name=»android.permission.READ_CONTACTS» />
<uses-permission android:name=»com.android.vending.BILLING» />
<uses-permission android:name=»android.permission.SEND_SMS» />
<uses-permission android:name=»android.permission.WRITE_EXTERNAL_ST ORAGE»/>
<uses-permission android:name=»android.permission.WRITE_INTERNAL_ST ORAGE»/>

Добавлено через 1 минуту
все работало, потом я открыл свой проект и сначало просто изменения сделанные в программе не были видны, а потом вообще при запуске ошибка. Код большой, покажу ток в функции onCreate, я так понял на нее ошибка указывает.
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

nobn=false;
play_potok1=play_potok2=false;
imageButton13=(ImageButton)findViewById(R.id.image Button13);
//local = new Locale(«ru»,»RU»);
df = DateFormat.getDateInstance(DateFormat.DEFAULT, local);
sqh = new base(this);
sqdb = sqh.getWritableDatabase();
tabs = (TabHost) findViewById(R.id.tabHost2);
tabs.setup();
TabHost.TabSpec spec = tabs.newTabSpec(«tag1»);
spec.setContent(R.id.tab1);
spec.setIndicator(getString(R.string.n91), getResources().getDrawable(R.drawable.liner));
tabs.addTab(spec);
spec = tabs.newTabSpec(«tag2»);
spec.setContent(R.id.tab2);
spec.setIndicator(getString(R.string.n92), getResources().getDrawable(R.drawable.tab_date_tim e));
tabs.addTab(spec);
mSettings = getSharedPreferences(APP_PREFERENCES, Context.MODE_PRIVATE);
if(mSettings.getString(«SETTINGS», «»).equalsIgnoreCase(«»)) SetSettings();
listView10=(ListView)findViewById(R.id.listView10) ;
listView11=(ListView)findViewById(R.id.listView11) ;
tsms=mSettings.getInt(«TSMS», 0);
rposition1=mSettings.getInt(«RPOS1», 0);
position1=mSettings.getInt(«POS1», 0);
position2=mSettings.getInt(«POS2», 0);
temail=tsms;
tabs.setCurrentTab(mSettings.getInt(«NUMTAB», 0));
maxsizesms=mSettings.getInt(«MAXSIZE», 0);
id1 = new ArrayList <Integer>();
message = new ArrayList <String>();
kcontacts = new ArrayList <Integer>();
kfiles = new ArrayList <Integer>();
tsend = new ArrayList <String>();
kolm1 = new ArrayList <Integer>();
id2 = new ArrayList <Integer>();
message2 = new ArrayList <String>();
kcontacts2 = new ArrayList <Integer>();
kfiles2 = new ArrayList <Integer>();
data2 = new ArrayList<String>();
time2 = new ArrayList<String>();
tsend2 = new ArrayList <String>();
kolm2 = new ArrayList <Integer>();
//set_list1();
//set_list2();
mAdapter1 = new MyAdapter1(this);
listView10.setAdapter(mAdapter1);
mAdapter2 = new MyAdapter2(this);
listView11.setAdapter(mAdapter2);
datep2=timep2=»»;
}

Добавлено через 1 минуту
я уже пробовал убрать код из onCreate, все равно ошибка.