crash | The code behind the LibreOffice crash reporter | Dashboard library

I have faced up with same problem. Try following: Open *.xib of your UITableViewCell as source code (Context menu / "Open As" / "Source Code"). Locate "tableViewCell" and "tableViewCellContentView" tags, delete its "translatesAutoresizingMaskIntoConstraints" attributes (with values), delete its subtags "autoresizingMask" if present.

https://i.stack.imgur.com/bDSJ3.png

We can use ego like below

Add mavenCentral() in Build Script

This issue was fixed by Google (10 February 2022).

You can now update Android Studio normally.

Please see my related answer I posted a couple of months ago on the Apple Developer Forums located at: https://developers.apple.com/forums/thread/681571?answerId=690251022#690251022 . Does this work for you?

Step 1. Update your targetSdkVersion and compileSdkVersion to SDK 31.

Step 2. Try to run any Foreground service when your app is in background. In my case, it was the widget's onUpdate method being called after updatePeriodMillis time, which will start a Foreground service, which updates the data by fetching appropriate information from internet.

Remember: The background execution limits added in Android 8.0 have nothing to do with this problem. This limitation/exception was added in Android 12/SDK 31 - Source.

Apps that target Android 12 (API level 31) or higher can't start foreground services while running in the background, except for a few special cases. If an app tries to start a foreground service while the app is running in the background, and the foreground service doesn't satisfy one of the exceptional cases, the system throws a ForegroundServiceStartNotAllowedException.

These special cases are:

• Your app transitions from a user-visible state, such as an activity.

• Your app can start an activity from the background, except for the case where the app has an activity in the back stack of an existing task.

• Your app receives a high-priority message using Firebase Cloud Messaging.

• The user performs an action on a UI element related to your app. For example, they might interact with a bubble, notification, widget, or activity.

• Your app invokes an exact alarm to complete an action that the user requests.

• Your app is the device's current input method.

• Your app receives an event that's related to geofencing or activity recognition transition.

• After the device reboots and receives the ACTION_BOOT_COMPLETED, ACTION_LOCKED_BOOT_COMPLETED, or ACTION_MY_PACKAGE_REPLACED intent action in a broadcast receiver.

• Your app receives the ACTION_TIMEZONE_CHANGED, ACTION_TIME_CHANGED, or ACTION_LOCALE_CHANGED intent action in a broadcast receiver.

• Your app receives a Bluetooth broadcast that requires the BLUETOOTH_CONNECT or BLUETOOTH_SCAN permissions.

• Apps with certain system roles or permission, such as device owners and profile owners.

• Your app uses the Companion Device Manager and declares the REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND permission or the REQUEST_COMPANION_RUN_IN_BACKGROUND permission. Whenever possible, use REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND.

• The user turns off battery optimizations for your app. You can help users find this option by sending them to your app's App info page in system settings. To do so, invoke an intent that contains the ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS intent action.

This will work for a while in Play Store until Google makes it mandatory to upgrade to API level 31.

Currently, starting November 2021 all apps must target API Level 30 and above. So if you're using API Level 31 for your app, downgrading your compileSdkVersion & targetSdkVersion to API Level 30 should fix the issue (atleast for a while).

If you were using Foreground service to do work that is time sensitive, start Foreground services within an exact alarm. Check out more about this from documentation here -> Set an exact alarm.

This is the solution that I ended up using for my app. Use WorkManager to schedule and start the background work. Check out more about this from documentation here -> Schedule expedited work.

You can know more about WorkManager here -> WorkManager

Github Repo for WorkManager samples -> WorkManager Samples

I added this answer specifically because searching for this exception does not bring up any resources to know why the service behaves differently on Android 12. All this is present in Google's documentation, and always remember to check the behaviour changes from the doc.

Everything related to this change can be found here -> Android 12 Behavior Changes, specifically within the Foreground Service launch restrictions.

1. It sounds strange, but the fix is adding work manager dependency 2.7.0+ : implementation "androidx.work:work-runtime:2.7.0"

2. You have to update dependencies that should support Android 12 braking changes (I had to update some third parties). Check that on github and documentation pages

3. Also, some libraries are using permission that is required for Android 12. Please check the documentation for this permission

4. Also, check google's issue tracker for google's library-specific issues related to Android 12

Maybe I missed something, but all this helped me to migrate. Good luck :)

For a while I was looking for a similar problem in reviews of popular live wallpapers. I found similar reviews only for one application. I updated my phone today. All my live wallpapers stopped working as expected. Then I installed "Earth & Moon" and this app works fine. It means that we are doing something wrong or, on the contrary, we are not doing something :) In the near future I will begin to investigate this problem.

I've been having the same problem (I'm on macOS Monterey), each time I try to take a screenshot the emulator crashes.

Sadly I haven't found a direct solution to this problem, that is a solution fixing the issue in the simulator. But I have learned that it is possible to take screenshots of the app from inside Android Studio, using Logcat.

Essentially, when you're running your app, if you go to the Logcat tab, there is a screenshot option which does seem to work without crashing. I've added a link to developer.android.com which explains how to do it.

Even thought this doesn't exactly fix the problem I hope it helps!

Take a screenshot (through android studio)

Edit:

I am happy to report that after a recent update for the emulator released by the developers, the issue no longer exists for me! The screenshot button has now started working again.

So if someone has the issue, I believe it can now be fixed by just updating your emulator to the latest version available.