ActivityManager | simple web system use for submitting file

The issue has been resolved after upgrading the realm to v10.20.0-beta.2

https://github.com/realm/realm-js/issues/4399#issuecomment-1061722341

First off- DashboardActivity.getInstance()- NEVER DO THIS. You're assuming there's exactly 1 instance of an activity at all times. That's wrong. There can be 0. There can be 2. You can't make an activity a singleton. In addition, this always creates a memory leak. NEVER store an Activity in a static variable, this is always a memory leak. It's also (due to the first fact) wrong because it can point to the wrong instance of an Activity.

Secondly- you're using getLastLocation. Don't do that. That function is meant for optimization and will usually return null (I know the docs say the opposite. The docs there have always been wrong.) If you need the location, request it instead. getLastLocation should only be used to get a quick result optimisticly before requesting location updates.

Thirdly- your call to requestNewLocation is passing in a location handler that does nothing. It isn't even updating mLastLocation because that's a method level variable and not a class one.

Fourthly- did you read the new rules for background location processing in ANdroid 12? https://proandroiddev.com/android-12-privacy-changes-for-location-55ffd8c016fd

Those are just the major mistakes, not smaller things that make me go "huh?". With the best of intentions here- this code needs major refactoring. It feels like someone who didn't really understand Android cobbled it together from a dozen examples he didn't understand. If I were you I'd start by simplifying the concept- do one thing, understand it, and then do another. You're overreaching your abilities at the moment doing this all at once, and you'll be better off learning one thing at a time.

In you NotificationBuilder you need to set notification category to NotificationCompat.CATEGORY_CALL and style to NotificationCompat.BigTextStyle() like this

In a comment you wrote:

I want to determine: should the app go through a fresh re-launch (app is killed) or just bring the app to front?

If you use a "launch Intent", this will handle all of this for you. If the app is already running, it will just bring the app to the foreground in whatever state it was in. If the app is not running, it will launch the app fresh.

To get a "launch Intent", you can use PackageManager.getLaunchIntentForPackage()

If somebody comes around the same problem. I was able to fix it by not using the signing function in Androidstudio but by manually using jarsigner and zipalign from java and the android-sdk-tools.

You're getting NPE because you are trying to create a new instance of your button before calling setContentView(R.layout.activity_main); This is what is causing your app to crash.

Consider changing your onCreate method to this snippet below:

I did more searching and finally found the answer... All credits go to the SO answer here:

https://stackoverflow.com/a/55712326/3718584

TLDR:

Had to change the intent from implicit to explicit due to API 21

After further research, it seems that according to the documentation, it simply isn't possible.

To help protect user privacy, Android 11 (API level 30) introduces limitations to when a foreground service can access the device's location, camera, or microphone. When your app starts a foreground service while the app is running in the background, the foreground service has the following limitations:

• Unless the user has granted the ACCESS_BACKGROUND_LOCATION permission to your app, the foreground service cannot access location.
• The foreground service cannot access the microphone or camera.

The user has to have some kind of active interaction with the app to allow the foreground service to start recording, such as displaying a notification that says "Tap here to start recording".

The fact that you're using the same name (in example 1), or even re-assigning to the same variable (in the first snippet of example 2) is inconsequential. A new object will be created, and the old object will be eligible for garbage collection.