Welcome to the Birder's Diary Forum for Support And General Questions

Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.

Mobile App won't em...
 
Notifications
Clear all

[Solved] Mobile App won't email sightings

Page 1 / 2

Posts: 3
Topic starter
(@skua29)
New Member
Joined: 10 months ago

Hello. Using V1.25 of the mobile app and on finishing outing if I press on send and close after filling in location, email, and comments the app will not close or send. It will continue to record time on the outing. If I press close only it will stop the outing, but on opening completed outings it will not send as email. If I persist in sending attempts I get a notice "Birder's Diary Mobile keeps stopping". Reinstalling did not help. Phone is Samsung S21 ultra. Permissions are allowed.

Thanks 

Ray

Reply
15 Replies
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Hi Ray,

You have the new S21 Ultra. Nice! How do you like it? I still have my S9+.

This is interesting. Your bug should be logged with my account in Google Play. Give me a day to dig into this and get you updated and get this hopefully resolved.

Stay tuned,

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Update, unable to get to this today. Will make it a priority tomorrow.

fyi

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Update:

I have isolated the problem you are having. It is all (100%) occurring on the latest version of Android (11) and all on the latest Samsung devices.

image

Digging into this. Stay tuned.

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Update:

I have found the problem. And can fix. However, the code is in the middle of a few big changes, so this may take some time. 4 days to 2 weeks.

You can probably fix this problem yourself. The problem is a CSV file in the Export/Import directory that has a filename I was not expecting. If you can clear that directory of all files, the problem should go away.

I assume this problem exists because you copied a checklist file of your own creation into this directory per the instructions here.

image

If you connect your phone to your computer and then browse that directory using Windows File Explorer, you should be able to remove the offending file(s).

Let me know please,

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Hmmm. Upon further review, this error should not keep BD Mobile from working correctly, as I have error trapping and avoidance built in.

All that to say, I am not certain that the previous post will fix your problem, but worth a try. If possible, before you delete files in that Local Storage Path on your phone, please take a screen capture and post here for my viewing.

Thanks.

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Update:

Testing on Emulated Pixel 4 XL with Android 11 (you appear to be running Android 11). I don't have your Samsung physical device nor is there an Emulator available for it.

I was able to reproduce the error that I see on your uploaded error report that occurs whenever BD Mobile encounters an error. It is a footprint that tells me where the error occurs. In this case...

image

So, I copied a file into that directory that is less than 9 chars in length (e.g. "abcd.csv"), and indeed it triggered the 

StringIndexOutOfBoundsException

But, it continues to open my selected email app (Gmail) and send the email. And you never see an error. This is how the code is supposed to work.

So, not sure why yours is hanging.

Digging deeper. Stay tuned...

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Ah! Got it. My bad. This error handler was added after I released v1.25.

So you do not have this code and this explains why you are getting this error!

The solution is to follow my instructions above for removing the errant file whose name is less than 9 chars total (e.g. "1234.678" - notice that the period/dot counts as a character).

Please let me know how that goes by posting back here once you try this and test it.

Thanks and sorry for the problem.

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Note: I should have a new version released with the corrected code in it soon (e.g. 4 days to 2 weeks).

You will be upgraded automatically if that is your Play Store setting on your device.

fyi

Jeff

Reply
Posts: 3
Topic starter
(@skua29)
New Member
Joined: 10 months ago

Thanks, waiting for a cable to connect phone to the computer and will try and find the offending checklist;

Reply
1 Reply
Admin
(@jeff)
Joined: 10 months ago

Member
Posts: 252
Posted by: @skua29

Thanks, waiting for a cable to connect phone to the computer and will try and find the offending checklist;

You don't need a cable and a connection to your computer; I just assumed that might be easiest for you.

Instead, you can download any of a number of "File Explorer"-type apps to find and remove the offending file.

To find the proper directory use the Search feature of the App to search internal storage (or perhaps SD card) for "*BDMOBILE*". At least one of these files should be in the directory with the offending file.

But now that I am trying this, I can't get it to work. I have ES Explorer app installed and I can't find this directory or files.

Not sure what is going on. I will update here when I have more info and a working solution.

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

Hi Ray,

I think the best thing to do is for me to release a quick update that fixes this issue. Expect an update Monday or Tuesday for this.

So sorry for the inconvenience. But I think this is the easiest way to get you back up and running the quickest.

fyi

Jeff

Reply
Posts: 252
Admin
(@jeff)
Member
Joined: 10 months ago

UPDATE:

Just released v1.27 to the Google Play Store. It contains the fix for this issue, and a couple other very rare (only happened once on old devices) issues.

Depending on your settings, it will auto-update on your device as soon as Google Play OKs it for release. Generally 4 to 24 hours.

Ray - please confirm that your problem is fixed when you get updated to v1.27.

image

fyi

Jeff

Reply
Page 1 / 2
Share: