Skip to content
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

Bug: entering long non-numeric housenumbers crashes the app #645

Closed
DaubnerF opened this issue Oct 12, 2017 · 5 comments
Closed

Bug: entering long non-numeric housenumbers crashes the app #645

DaubnerF opened this issue Oct 12, 2017 · 5 comments
Assignees
Labels
bug feedback required more info is needed, issue will be likely closed if it is not provided

Comments

@DaubnerF
Copy link

I am fairly new to StreetComplete, but today managed to reproducibly crash the app by entering a housenumber with a certain format:

The house was part of a larger row-house complex, so on the sign it said 25/11 (house number 25 house 11). This is quite a common naming scheme here in Austria.

When I tried to enter 25/11 (by switching to the normal keyboard) the app crashed in a reproducible way. Entering 25/1 (or any other single-digit number at the end) works fine.

@MPoppinga
Copy link

I had the same issue when trying to tag a building with "10,10a". This should be a valid value according to https://wiki.openstreetmap.org/wiki/Addresses#Buildings_with_multiple_house_numbers .

@westnordost westnordost self-assigned this Oct 12, 2017
@westnordost
Copy link
Member

Which version are you using?
Are you using the version from google play or from F-Droid? If it is from F-Droid, you are asked to send the bug report - in that case, could you do that? For Google Play, I think I get the crash reports automatically - but if in case you are asked, could you press "yes"?

@westnordost westnordost added the feedback required more info is needed, issue will be likely closed if it is not provided label Oct 12, 2017
@MPoppinga
Copy link

I'm using the current master but I could reproduce it also on the current beta version in GooglePlay (2.1). I submitted a feedback from the crash dialog.

@DaubnerF
Copy link
Author

DaubnerF commented Oct 13, 2017

I'm using the version from Google Play. I was asked if I want to send the crash report and I already did that before I opened this issue. If you did not get the report, I can either try to reproduce the issue and send the report again or do something else which helps you in identifying the issue.
Edit: my current version is 2.1

@westnordost
Copy link
Member

westnordost commented Oct 13, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feedback required more info is needed, issue will be likely closed if it is not provided
Projects
None yet
Development

No branches or pull requests

3 participants