Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only.

    Please, do not make any changes to your username or email addresses at id.unity.com during this transition time.

    It's still possible to reply to existing private message conversations during the migration, but any new replies you post will be missing after the main migration is complete. We'll do our best to migrate these messages in a follow-up step.

    On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live.


    Read our full announcement for more information and let us know if you have any questions.

Bug Crash on android with TouchScreenKeyboard.Open

Discussion in 'Input System' started by Apollo-Meijer, May 9, 2020.

  1. Apollo-Meijer

    Apollo-Meijer

    Joined:
    Mar 30, 2015
    Posts:
    31
    Hey!

    I had a Crash on android (native crash) and I got it pinned down to the new Input system that was enabled in the project.

    when calling:
    Code (CSharp):
    1. TouchScreenKeyboard.Open("", TouchScreenKeyboardType.Default, false,
    2.                                 false, false, false, "Type a message here...");
    And you enter more than 50+ characters in the text field it crashes the application the native level.

    I got this reproduced on an empty project and setting the input system to use "Both" is what causes the issue.
    I don't even use the new Input system but it got added as a dependency. Setting the input system to the old one solved this crash.

    I added a project to make it easier to debug for you, just build the project to phone and press the "Button" and add a lot of test to the input field. You don't need to add a lot of text tbh.

    You do need to set it to use Both and maybe add the package again but you will get it.
     

    Attached Files:

  2. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,570
    Hey. Could you please file a bug report with this info?