Pleco for iOS 3.1.4 Beta

[mikelove]

Well, right now we ignore "skip if no recording" and always skip if TTS is installed, so I suppose it wouldn't make things any more complicated if we simply set "skip if no recording" to be on by default with TTS installed and let people turn it off.

 

[ACardiganAndAFrown]

Excellent, I'm very pleased with this. Noticed one bug though: words selected through history, specifically dictionary history (search, reader, etc. don't seem to be effected) still play TTS - maybe it's words that I've played before?

Side note: love the underlining of entry words in sample sentences, brilliant!

 

[Shun]

I hope it isn't too late now for another bug report. I first thought it was a rare case, it happened in beta 2, then in beta 3, and now in the GM. On backing up the Flashcard database, I get the message "Backup Failed, Flashcard database backup could not be completed successfully". It does back up if I first close Pleco completely. After going into Organize Flashcards and opening any card, the backup fails. Perhaps the flashcard database file is in use, so the backup function cannot access it.

 

[weingin]

Small bug report:

I'm on 3.1.4 GM and just tried to do 'Still OCR', then chose 'Take Picture' and everytime I hit the trigger, Pleco crashed. Reproducable on my 5s (latest iOS 7).
...Alright, now it's working fine again, not reproducable anymore. I've tried the same thing on my friends iPhone 5 (also no 3.1.4 GM). It worked on his device. Then, I wanted to show him the bug on mine, and - hurray - it worked on mine. So I guess nevermind?

 

[mikelove]

@ACardiganAndAFrown - thanks! Underlining seemed logical in cases where we don't have a bold font, yes; I'm worried a few people may object to it / demand an option to disable it, but we made that change on Android a week ago and nobody's complained there yet so I'm hopeful it'll be consistently well-received.

@Shun - thanks! Not too late - have to resubmit anyway since we found a new multi-choice bug (and while we're at it we think we have a way to address the worst of the overlapping-TTS-audio issues).

@weingin - thanks - we'll see if we can come up with any explanation / reproduction steps but it doesn't sound too severe anyway.

 

[weingin]

@weingin - thanks - we'll see if we can come up with any explanation / reproduction steps but it doesn't sound too severe anyway.

Actually it's not a Pleco bug, it's iOS itself. I just started the camera app from control center and it crashed in the same way as previously when Pleco was using it. So nothing to worry about on your end.

 

[mikelove]

@weingin - thanks for the follow-up; sorry it's misbehaving for you in general but it's certainly a relief on our end.

@Shun - turns out this was actually a rather severe / subtle little bug that could potentially cause all kinds of problems after visiting Card Info, so thanks very much for pointing it out - would have been well worth pulling + resubmitting even if it was just to fix this.

 

[Shun]

You're welcome! I've been using Pleco quite intensively during the beta phase -- is there any chance the flashcard database got corrupted, or did the dangers lie at another level? Fortunately, I took a backup at each step along the way, so it would be easy to go back.

 

[mikelove]

It wouldn't cause corruption, no - it would just cause the database to be stuck in a 'locked' state, so the worst that would happen would be that a couple of modifications you made might not have been saved correctly. (but that would still happen cleanly - they'd be totally missing)

 

[Shun]

Another little bug report: I took this screenshot yesterday running GM 1. Probably the "variant of" line wasn't parsed correctly, or something like that.

 

[mikelove]

Thanks - not sure if we can fix this one for the resubmit or not, we'll see.

 

[ACardiganAndAFrown]

1. Just went to add-ons and clicked restore itunes purchases and got this funky looking message:

2. Audio is still acting a little weird
for the entry 哈喇/拉子
clicking PY audio: first I get female stitched together audio / the second time I get male TTS... [I don't have female TTS installed so I don't know if that would ever "come into play" but male stitched together audio is not getting played in this entry, at least)

 

[mikelove]

@ACardiganAndAFrown - 1) is normal if you're using a copy of Pleco not downloaded from Apple. For 2), falling back on the male TTS is the default behavior for words that don't have exact matches in the audio database, but you can override that in Settings / Audio.

 

[Alexis]

Sorry, this is not very helpful, nor can I reproduce it anymore, but:

Beta release 2 was not working on my iPad 3 (wrong ARM compliation issue), but I needed Pleco, so I nuked Pleco and reinstalled from scratch.
Every time I tried to use "send to" from Safari with an epub, or tried to access my dropbox folder from within Pleco, Pleco would crash.
I then tried with The "beta" (ie. non-release) version of Beta Release 3, and was seeing the same issue.
I don't see it anymore with Release 4, but I also had tried loading a PDF first, which (possibly) seemed to make things go smoothly after.
I checked the ~Library/Logs/CrashReporter/MobileDevice/* for crash logs after syncing, but nothing showed up for Pleco

 

[Shun]

Bug report: Tapping on "领带" leads me to the ".45" definition. It works fine in the Dictionary part of the app.

 

[mikelove]

@Alexis - do you remember if the release version was still installed when you saw the issue with the beta? We haven't changed really any of the code related to this so my initial suspicion would be that this has something to do with the installation rather than 3.1.4.

@Shun - no luck reproducing this one; does it happen consistently?

 

[Shun]

Yes, it also just happened with "近亲" inside the "近" OCC dictionary definition inside Flashcards. You would need to create a custom flashcard of "近", then start a test containing it, answer it, tap over to the OCC dictionary, then tap on a linked word after a > symbol, and you should get the ".45" definition of the 21C dict.

 

[mikelove]

@Shun - thanks; reproduced now, though since we already resubmitted 3.1.4 it won't be fixed in that unless some other more serious bug forces us to resubmit again. But it'll be fixed in 3.2 (or, if other bugs force it, 3.1.5) regardless.

 

[goldyn chyld]

Has Apple approved the update yet?

 

[mikelove]

Nope, still waiting. Hopefully tomorrow, though we'd probably wait until Monday to release it since if there's a horrible bug we'd like to be able to beg Apple for a quick review of the fix for it while they're actually at work.