iOS / iPadOS: Viewing vault item causes crash #1512

Closed
opened 2025-11-26 22:51:13 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @Private-Fragrance on GitHub (Oct 13, 2022).

Steps To Reproduce

(I'm new to GitHub; someone said I should report this here --I don't see an iOS client option for bugs...?)

This affected both iPhone and iPad apps. I had one entry that I could not view as it would immediately cause the app to crash.

Luckily I was able to view it in the web vault so I could fix it.

Somewhat inconclusive but still useful research:

  1. When I cloned the item, the clone crashed too
  2. The item had a custom field with an emoji -- on a hunch I removed the emoji. (Call this Custom Field A)
  3. The item also had two custom fields with identical titles, on a hunch I changed one of them. (They had identical titles but different content.) (Call these Custom Field B and Custom Field C)
  4. Those two things made it so the cloned item would launch properly. I then made the same changes to the original entry and it launches properly now. Problem solved.
  5. ...what's inconclusive is that removing ONLY the emoji or removing ONLY the duplicate custom field title did not fix the issue. It was only when I removed both.

Expected Result

View vault item

Actual Result

Unable to view vault item due to app crashing when accessing that specific item

Screenshots or Videos

No response

Additional Context

No response

Operating System

iOS

Operating System Version

iOS 16.x & iPadOS 15.x

Web Browser

Safari

Browser Version

No response

Build Version

2022.9.1 (2147)

Originally created by @Private-Fragrance on GitHub (Oct 13, 2022). ### Steps To Reproduce _(I'm new to GitHub; someone said I should report this here --I don't see an iOS client option for bugs...?)_ This affected both iPhone and iPad apps. I had one entry that I could not view as it would immediately cause the app to crash. Luckily I was able to view it in the web vault so I could fix it. Somewhat inconclusive but still useful research: 1. When I cloned the item, the clone crashed too 2. The item had a custom field with an emoji -- on a hunch I removed the emoji. (Call this Custom Field A) 3. The item also had two custom fields with identical titles, on a hunch I changed one of them. (They had identical titles but different content.) (Call these Custom Field B and Custom Field C) 4. Those two things made it so the cloned item would launch properly. I then made the same changes to the original entry and it launches properly now. Problem solved. 5. ...what's inconclusive is that removing ONLY the emoji or removing ONLY the duplicate custom field title did not fix the issue. It was only when I removed both. ### Expected Result View vault item ### Actual Result Unable to view vault item due to app crashing when accessing that specific item ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System iOS ### Operating System Version iOS 16.x & iPadOS 15.x ### Web Browser Safari ### Browser Version _No response_ ### Build Version 2022.9.1 (2147)
GiteaMirror added the bug label 2025-11-26 22:51:13 -06:00
Author
Owner

@djsmith85 commented on GitHub (Oct 13, 2022):

@Private-Fragrance Thank you for the report and I have moved it to the bitwarden/mobile repository.

@djsmith85 commented on GitHub (Oct 13, 2022): @Private-Fragrance Thank you for the report and I have moved it to the bitwarden/mobile repository.
Author
Owner

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/2131

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2131
Author
Owner

@Greenderella commented on GitHub (Aug 5, 2024):

Hi there,

I attempted to reproduce your issue and was unable to do so.

I have items created as early as April 2020, some with attachments and some without, and some with custom fields and some without. All of these items can be viewed, cloned, launched, and edited (including adding and removing emojis/custom fields) as expected on iPadOS 17.6.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

@Greenderella commented on GitHub (Aug 5, 2024): Hi there, I attempted to reproduce your issue and was unable to do so. I have items created as early as April 2020, some with attachments and some without, and some with custom fields and some without. All of these items can be viewed, cloned, launched, and edited (including adding and removing emojis/custom fields) as expected on iPadOS 17.6. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

@Private-Fragrance commented on GitHub (Aug 15, 2024):

@Greenderella
I have a new test that provides a fairly consistent app crash:

  • Make a new entry
  • Enter some Name and create a simple Password if you want. Maybe add few things to the Notes area.
  • Create a Custom field (“text”)
  • My “corrupted” entry had a bunch of custom Text fields but one had ~300 characters without spaces, ~350 with spaces. It had a bunch of uninteresting characters but it did have unbroken strings of hyphens, @ signs and capitalized English words. So copy and paste some of these. Perhaps worth noting that some of the hyphens were unbroken in a long string, like a divider.
  • Save the item.
  • Go back in and play with the Favorites toggle and move it in and out of various folders. Eventually both iOS and iPadOS should crash, usually on Save. It may take a few tries and it seems to be fairly random. But toggling Favorites and moving in and out of folders seems to do the trick.
  • Worth noting that I also made a fresh entry with almost nothing in it. Just a Name. I did the same Favorites toggling and moving Folders —no issue there. But immediately I’d have issues with the aforementioned fresh entry with the suspect Text field.
@Private-Fragrance commented on GitHub (Aug 15, 2024): @Greenderella I have a new test that provides a fairly consistent app crash: - Make a new entry - Enter some Name and create a simple Password if you want. Maybe add few things to the Notes area. - Create a Custom field (“text”) - My “corrupted” entry had a bunch of custom Text fields but one had ~300 characters without spaces, ~350 with spaces. It had a bunch of uninteresting characters but it did have unbroken strings of hyphens, @ signs and capitalized English words. So copy and paste some of these. Perhaps worth noting that some of the hyphens were unbroken in a long string, like a divider. - Save the item. - Go back in and play with the Favorites toggle and move it in and out of various folders. Eventually both iOS and iPadOS should crash, usually on Save. It may take a few tries and it seems to be fairly random. But toggling Favorites and moving in and out of folders seems to do the trick. - Worth noting that I also made a fresh entry with almost nothing in it. Just a Name. I did the same Favorites toggling and moving Folders —no issue there. But immediately I’d have issues with the aforementioned fresh entry with the suspect Text field.
Author
Owner

@Private-Fragrance commented on GitHub (Aug 15, 2024):

@Greenderella
Elaborating on my previous comment, one of the crash-prone entries did not crash as soon as I removed the custom text field (with the hyphens etc.)

Thanks

@Private-Fragrance commented on GitHub (Aug 15, 2024): @Greenderella Elaborating on my previous comment, one of the crash-prone entries did not crash as soon as I removed the custom text field (with the hyphens etc.) Thanks
Author
Owner

@Greenderella commented on GitHub (Aug 15, 2024):

Hi @Private-Fragrance,

My “corrupted” entry had a bunch of custom Text fields but one had ~300 characters without spaces, ~350 with spaces. It had a bunch of uninteresting characters but it did have unbroken strings of hyphens,

This issue seems similar to the one described here: https://github.com/bitwarden/mobile/issues/3330 🤔

Could you please try to replicate this problem using the beta version as well? You can join the beta program and download the app following these steps: https://community.bitwarden.com/t/about-the-beta-program/39185

Given the recent updates to the beta builds, it would be beneficial to verify if the issue persists with the latest version.

Thanks for your assistance, and I eagerly await your feedback!

@Greenderella commented on GitHub (Aug 15, 2024): Hi @Private-Fragrance, > My “corrupted” entry had a bunch of custom Text fields but one had ~300 characters without spaces, ~350 with spaces. It had a bunch of uninteresting characters but it did have unbroken strings of **hyphens**, This issue seems similar to the one described here: https://github.com/bitwarden/mobile/issues/3330 🤔 Could you please try to replicate this problem using the beta version as well? You can join the beta program and download the app following these steps: https://community.bitwarden.com/t/about-the-beta-program/39185 Given the recent updates to the beta builds, it would be beneficial to verify if the issue persists with the latest version. Thanks for your assistance, and I eagerly await your feedback!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1512