124 fc when sync asks to confirm deletions

[bettertthan74]

I am using build 1630 of MMW
I am using wifi sync. Syncing using playlists , about 1400 tracks.
I uninstalled the app and deleted all of the mediamonkey folders on my external and internal storage and then installed 124 from google play
Syncing goes through the analyze step, I see the confirm message on my status bar and then get a report or close dialogue.
all of my music syncs to the external card on my android and I have not used usb sync.
running pac-man rom 10.1

I sent logs at about 9:30pm eastern

[bettertthan74]

I had posted this before but deleted it because I couldn't repeat it. I was able to 2x's now.

If MMA is syncing over wifi and is in the background and the confirm delete box pops up, attempting to get to the box crashes mma. If MMA is in the foreground when it pops up , then you can hit ok, but like in previous versions, the box doesn't go away, but the sync will complete behind it

[bkenobi69]

I had a similar issue where the confirm delete was somehow lost in the background and I could not get it back. Basically, confirm delete showed up, somehow I missed it (not sure how it disappeared) and the sync went on without any additional progress. The confirm delete was visible in the drop down menu, but selecting it did not restore it. I selected "cancel" and "Terminate" sat on the screen for several minutes prior to my killing the app manually.

[bettertthan74]

I am seeing the same behavior on mma 145. Even a text message pop up is enough to cause a problem. Is there a issue created for this?

[Lowlander]

You should be able to send a log from MMA from Options.

[Jonny2284]

Do you still need a log to look at for this issue? I'm having it when trying to sync as well, if I can keep the phone awake long enough to catch the confirm box it's fine, if not the sync stalls.

[bkenobi69]

Same issue here. I uploaded some logs for a different topic a couple weeks ago to a help ticket. The last response indicated this would be fixed in the next release, but when 148 came out, it was not fixed. Perhaps the problem is fixed in the code but that fix didn't make the last cut? Either way, I can provide another log if more examples are needed.

[Jonny2284]

Any progress on this issue? At least an affirmation that's it's being looked at?

Can't help but think it's being ignored because of the topic title despite the issue persisting in the latest build.