IMediaPicker.CapturePhotoAsync resumes app from splash screen

Question

IMediaPicker.CapturePhotoAsync resumes app from splash screen

Bruno Teodori 20

Hi, I've been experiencing this problem in Maui when accessing either CapturePhotoAsync() or PickPhotoAsync(): the app is sent to background either to open the camera or the gallery, once the taken photo or the chosen one are confirmed the app is resumed but it's sent back to its splash screen resulting in the caller method being unable to complete. This happens on Android devices, about 95% of the times on physical device (I'm testing it on a Redmi with android 11.0 api 30), less frequently on emulators (tested both on android 11.0 api 30 and 13.0 api 33).

I can't tell about IOS because I haven't tested it yet.

Here's a sample of my code (that sits in a viewmodel inside a RelayCommand):

1     if (mediaPicker.IsCaptureSupported)
2     {
3	     MainThread.BeginInvokeOnMainThread(async () => {
4		    FileResult chosenPhoto = await mediaPicker.PickPhotoAsync();
5		        	if (chosenPhoto != null)
6			        {
7				      //do something with the picture
8                   }
9                  else
10			        {
11  				     //well something's gone wrong
12			        }
13 	      });
14    }

At line 4 the camera opens, the debugger stops and when i confirm the photo taken or the one picked from the gallery the app doesn't resume where i left but it restarts from its splash screen. Am I doing something wrong here?

I've been struggling with this for a while now and searched all over the internet, but I've found no solution, can anyone help me please?

Anonymous

2023-07-21T09:20:54.8433333+00:00
When you pick a photo, your application will be moved to background code. After picking a photo, you cannot resume application in the debug mode?

If so, firstly, you can popup a display alert after you choose the photo like following code.

if(chosenPhoto != null){ await DisplayAlert("info", chosenPhoto.FileName,"OK"); }

Then you can debug it to make this application installed in your android device. After that, you can click you application directly in your device without debug mode. if you can get the alert when you back to your application. If you can get the alert with correct file name, no need to worry about it. You application was killed by the MIUI in the debug mode.
Bruno Teodori 20 Reputation points

2023-07-21T09:51:27.03+00:00

Hi Leon, thank you for your quick reply, it doesn't "break" only in debug mode, it breaks also in release. It's sent to background and when it's resumed it restarts from the splash screen, so it never hits the line "if(chosenPhoto != null)". Sometimes it doesn't even go back to foreground.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bruno Teodori 20 Reputation points

2023-07-24T13:48:38.73+00:00

Hello,

I'm afraid you answered another question here....
Anonymous

2023-07-25T00:59:40.41+00:00

Based on your description, it looks like your application killed by the android OS. You can set your application to lock Background mode, then test it, if this issue will disappear.
Bruno Teodori 20 Reputation points

2023-07-25T09:24:09.68+00:00

Hi Leon, I confirm the app gets killed when it's sent to background. When the camera opens this is what my device's log (logcat) says: Xiaomi M2006C3LVG Info 364 lowmemorykiller Kill 'com.myapp.app' (31322), uid 10280, oom_adj 501 to free 186220kB; reason: device is not responding.
Anonymous

2023-07-28T07:56:42.33+00:00

Could you change other devices to make a test? If other devices work normally?
Bruno Teodori 20 Reputation points

2023-07-28T09:04:18.01+00:00

I tested it on another device and it works just fine, so I guess it's lack of memory on my own device that's causing the issue.
Bruno Teodori 20 Reputation points

2023-07-28T09:05:36.93+00:00

I tested it on another device and it works just fine, so I guess it's a lack of memory on my own device that's causing the issue.
Anonymous

2023-07-28T09:17:34.9033333+00:00

I convert my comment to answer, if this issue is disappeared by changing other devices, please accept answer, it will help others who have similar issue.

Accepted answer

0 additional answers

Your answer

Anonymous

2023-07-21T09:20:54.8433333+00:00

When you pick a photo, your application will be moved to background code. After picking a photo, you cannot resume application in the debug mode?

If so, firstly, you can popup a display alert after you choose the photo like following code.

if(chosenPhoto != null){ await DisplayAlert("info", chosenPhoto.FileName,"OK"); }

Then you can debug it to make this application installed in your android device. After that, you can click you application directly in your device without debug mode. if you can get the alert when you back to your application. If you can get the alert with correct file name, no need to worry about it. You application was killed by the MIUI in the debug mode.
Bruno Teodori 20 Reputation points

2023-07-21T09:51:27.03+00:00

Hi Leon, thank you for your quick reply, it doesn't "break" only in debug mode, it breaks also in release. It's sent to background and when it's resumed it restarts from the splash screen, so it never hits the line "if(chosenPhoto != null)". Sometimes it doesn't even go back to foreground.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bruno Teodori 20 Reputation points

2023-07-24T13:48:38.73+00:00

Hello,

I'm afraid you answered another question here....
Anonymous

2023-07-25T00:59:40.41+00:00

Based on your description, it looks like your application killed by the android OS. You can set your application to lock Background mode, then test it, if this issue will disappear.
Bruno Teodori 20 Reputation points

2023-07-25T09:24:09.68+00:00

Hi Leon, I confirm the app gets killed when it's sent to background. When the camera opens this is what my device's log (logcat) says: Xiaomi M2006C3LVG Info 364 lowmemorykiller Kill 'com.myapp.app' (31322), uid 10280, oom_adj 501 to free 186220kB; reason: device is not responding.
Anonymous

2023-07-28T07:56:42.33+00:00

Could you change other devices to make a test? If other devices work normally?
Bruno Teodori 20 Reputation points

2023-07-28T09:04:18.01+00:00

I tested it on another device and it works just fine, so I guess it's lack of memory on my own device that's causing the issue.
Bruno Teodori 20 Reputation points

2023-07-28T09:05:36.93+00:00

I tested it on another device and it works just fine, so I guess it's a lack of memory on my own device that's causing the issue.
Anonymous

2023-07-28T09:17:34.9033333+00:00

I convert my comment to answer, if this issue is disappeared by changing other devices, please accept answer, it will help others who have similar issue.

Answer 1

Hello,

I guess it's a lack of memory on my own device that's causing the issue.

Correct, the problem you are experiencing is likely due to limited device memory. To mitigate this issue, it would be advisable to consider using an Android device with a higher memory capacity. This will help ensure smoother performance and accommodate the resource requirements of the application.

Thank you for your understanding.

Best Regards,

Leon Lu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

IMediaPicker.CapturePhotoAsync resumes app from splash screen

0 additional answers

Your answer