- Bear Version: 2.3.12 (13245)
- OS Version: iPadOS 18.3.2
- What were you doing: annotating a screenshot image in a note
- What feature did you use: annotate
- What happened: the annotations I made repeatedly failed to save after I hit “done”
- What did you expect to happen: the annotations I made would be saved
I am experiencing this issue more and more frequently where annotations I make to images or PDF’s with my apple pencil don’t save when I hit “done” and instead just vanish. I haven’t done any extensive testing, but for me this usually happens when I am annotating a screen shot I have taken on my iPad in a note, but I have also had it happen when annotating PDF’s as well. It’s super frustrating to have taken time to annotate an image or PDF only to have all your work suddenly and unexpectedly just vanish when you think you’re done, and especially so when it seems like you never know when it’s going to happen. Any help would be much appreciated.
1 Like
I was able to do a little more testing and was able to reliably reproduce the problem for images (still not sure what’s happening with PDF’s)…
- when taking a screenshot on the iPad…
- if you select
- “copy” from the “share” menu
- or “copy and delete” from the “Done” menu
- and then paste that image into a note, the screenshot is saved as some type of generic image file in Bear
- and as a result will ALWAYS fail to save annotation
- Conversely, if you select…
- “save to photos” from the “Done” menu
- and then add the photo to the note from BIU keyboard, the screenshot is saved as a PNG in Bear
- then there are NO issues with saving the annotations
Hopefully this helps narrow down the issue (for images at least) and gives you guys some insights into a possible solution?
I suspect this problem is caused by an iOS file date bug we recently found. We found a workaround, and we’ll ship it with the next update.
2 Likes
Based on my own experience with 2.4 and THIS recent bug report it appears this issue has not been resolved yet.
Yup, I’m seeing this bug as well on 2.4.
2.4.1 fixed this for my iPhone.
