-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit Note confirmation crash #4200
Comments
|
FYI If the error occurs only with "Don't keep activities" (or better, if it is Flavio On Fri, 8 Apr 2016 at 10:51 Mark Carter [email protected] wrote:
|
BTW, I noticed that ACRA is throwing some odd errors and these are mentioned in this issue here. Any plans to update ACRA plugin to the latest (4.8.5)? It requires some code changes (I just saw that it introduces compiler errors when dropped in). |
I am experiencing crashes upon clicking the check mark to confirm edit of a card. But it only happens on my tablet and not on my phone. It has been happening on all versions, both released and beta. AnkiDroid Version = 2.6beta6 Android Version = 5.1.1 ACRA UUID = 26e71aac-7146-4f05-a37d-c75f00115e40 |
The crash signature from your device appears to be the same as above. Do you happen to have the |
Indeed I did have it set. Turning it off resolved the crash. On 6/12/2016 4:37 AM, Houssam Salem wrote:
|
I'm not certain if this is the right place to report it, but I can't edit notes in the android version. Tapping the checkmark causes a 'AnkiDroid has encountered a Problem. A report is being sent to the developers.' error and the edit is not saved. Hardware/OS To reporoduce: frequency: 100% of the time, I can only edit using the desktop client AnkiDroid version: ankidroid just updated for me today (nov 12/2017) but the problem persists. Note: I'm a software engineering intern looking for side projects. It might be fun to chip in on fixing this. I've never contributed to OSS however (Java, correct?). Please let me know if anybody has an interest in this who could also point me at how to get started. |
Did you read the previous comments? Do you have that setting enabled? |
My situation has changed and I won't be able to work on any side projects for a while. Pardon my not being able to follow through. |
Looking at this - @timrae you interested in a PR for an upgrade to ACRA 4.x-current? |
There was an issue last time I updated Acra and had to revert: |
Theoretically it should be fixed by ACRA/acra#344, so I think ok to give 4.11 a try, but we'll need to tread lightly. Please put it into its own PR if you do submit one. |
Agreed on treading lightly - introducing an error in the error-reporting function is serious problem. I already have it working but its the testing I'm struggling with and that's where I want to suss out things like the issue you linked above. I'll give it a shot, definitely in a separate PR. I still need to get better at Activities etc so ideally I can take a look at the real core issue here and have a go at it later (separately) as well |
@javenschuetz if you're still around I'm more interested in fixing this now - previously I was using this as my 100%-reproducible test case to trigger crashes so I selfishly didn't want it to go away ;-), but I have a test crash button now. I'm 99% sure this is a simple issue of not saving / restoring bundle state correctly, and if you ever wanted to learn android and fix a bug at the same time, our code has examples of bundle save/restore all over to look at while the change itself should be pretty self-contained. Great first issue... |
I'm actually free to work on things for the next 6 months or so, thanks for the mention I haven't personally seen the issue in months however and thought it was fixed. Is this still happening, or are you talking about a related issue? edit: I'm probably going to be AWOL for 2 days while I work on an openGL assignment, I'll check back after its done :) |
Hmm - maybe in one of the library updates as I was forward-porting it "self fixed" but I don't think so - last I checked it was still a crash bug even if only because of rare settings. If not this one (and you're still interested in poking around) I made a "Good First Issue!" label and there are a few that might be fun (?) to chew on. |
I'm going to check back with you in late December/early January after this semester ends and I end up with way more time. I might lurk a bit until then asking questions if I find time though |
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
…ki-Android into buggy-ankidroid#4200 # Conflicts: # AnkiDroid/src/main/java/com/ichi2/anki/DeckPicker.java # AnkiDroid/src/main/java/com/ichi2/anki/NoteEditor.java # AnkiDroid/src/main/java/com/ichi2/anki/Reviewer.java # AnkiDroid/testconfig.gradle
AnkiDroid 2.5.4 (Android 6.0.1).
Try this:
This happens for any note in any deck. There is no error when editing a note selected via the Card Browser.
The text was updated successfully, but these errors were encountered: