-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Android Question Notification entering app
- Thread starter Scantech
- Start date
Similar threads
B4A Tutorial Automatic Foreground ModeB4A Tutorial android.jar / targetSdkVersion / minSdkVersion
B4A Tutorial Geofence - Monitoring a region in the background
B4A Tutorial Integrating Firebase Services
Other Firebase Notifications & Firebase Auth Issues
B4A Tutorial Background location tracking
Where is the error message?
If i go to Activity Dashboard and click Home button, then i click system app Icon it goes where it is suppose to be in Dashboard. But the notification behaviour is different. It goes directly to Main and this will definitely cause some issues. I do call ApplicationExit with main.
I want avoid this issue and not allow user to enter app with the click of notification.
I want avoid this issue and not allow user to enter app with the click of notification.
This is what i was looking for
It was set to Main previously. Pass an empty string will not allow it to enter app.
I guess my app can't function properly if its not returned back to where it is suppose to be.
B4X:
notification.SetInfo("OBD2 Status", Body, "")I guess my app can't function properly if its not returned back to where it is suppose to be.
There are 2 crashes the first one i don't understand and second in comserial i can understand that one.
If you look in the above Quote "ERROR ACTIVITY RESUME IN DASHBOARD"
It crashed because of this (Pager not initialized?)
Also, why it killed Main Instance (See QUOTE above)?
I don't think any of this is in the tutorial section. lol
If you look in the above Quote "ERROR ACTIVITY RESUME IN DASHBOARD"
It crashed because of this (Pager not initialized?)
I have this in Dashboard Activity Resume (Starter.atPage is int)
and this is Dashboard Activity Create (8 panels are created)
By Exiting Dashboard Activity(Not UserClosed) using home button, entering Main Activity from Notification, User Exiting Main Activity will go to Dashboard Activity, where Dashboard was still active(Not UserClosed) by Home button and then it will Create Dashboard Activity (Why Create???) and Resume. I don't understand why it says Pager not initialized and why it Created Dashboard where it should of been Resume only? This is not a typical correct behavior? Is the Error because it created new instance and did not kill the old Dashboard instance?
Also, why it killed Main Instance (See QUOTE above)?
I don't think any of this is in the tutorial section. lol
Last edited:
1. A different activity was started.
2. The Home button was pressed
3. A configuration changed event was raised (orientation changed for example).
4. The Back button was pressed.
In scenarios 1 and 2, the activity will be paused and for now kept in memory as it is expected to be reused later
This should of applied to Main activity behavior but it is not. Previous Main instance got killed.
2. The Home button was pressed
3. A configuration changed event was raised (orientation changed for example).
4. The Back button was pressed.
In scenarios 1 and 2, the activity will be paused and for now kept in memory as it is expected to be reused later
This should of applied to Main activity behavior but it is not. Previous Main instance got killed.
Last edited:
More testing with more results.
This one is good.
My app can handle it very well if i do not use ExitApplication in Main
ExitApplication has a weird behavior which remain unanswered ...why the pager did not get initialized.
You notice my Services did not get destroyed with ExitApplication called after StopService. I think i need to remove ExitApplication. It was used, because i had an issue with one of the device back 10 years ago where bluetooth gets hanged and could not reinitialized astream or something like that. I did workaround by using ExitApplication.
This one is good.
My app can handle it very well if i do not use ExitApplication in Main
As you can see no errors.
ExitApplication has a weird behavior which remain unanswered ...why the pager did not get initialized.
You notice my Services did not get destroyed with ExitApplication called after StopService. I think i need to remove ExitApplication. It was used, because i had an issue with one of the device back 10 years ago where bluetooth gets hanged and could not reinitialized astream or something like that. I did workaround by using ExitApplication.
Last edited:
Erel has in the past discouraged the use of ExitApplication. He said this:
"The OS will treat your app as if it has crashed when you call ExitApplication. In some cases it will try to restart it automatically."
Bottom line, it is not a reliable way to terminate an application.
"The OS will treat your app as if it has crashed when you call ExitApplication. In some cases it will try to restart it automatically."
Bottom line, it is not a reliable way to terminate an application.