2017f Problems with Input on Windows Universal platform
I've looked through the board, including the similarly named entry, but I do not see a solution for this bug.
Using 2017f.4, my project works fine as a Standalone app, but when I switch the platform to Windows Universal Platform, I get a NullException error in the CrossPlatform Mobile script, and then Input fails to work completely.
To replicate: Just make a simple app with input, change it to Universal Windows Platform, then try to run it. There will be no input.
I've tried: Deleting the Input Folder and having it "reset." That takes it back to standalone and input works, but converting it back to Universal Windows Platform causes Input to fail. I've tried changing the input source to Independent Input Source, no change.
I tried 2018, and there are so many updates to it, and so many things that no longer work (like Substances), I cannot take my projects, some of which date back to 4 or 5, and use it.
Theory: Whatever is throwing the null exception in CrossPlatform input is causing the input system to crash, and not accept any more input. I don't need mobile input, so if I could just disable that, it might work?
UPDAT$$anonymous$$... So, I was able to get my app's input to work, by disabling the $$anonymous$$obile Input via the $$anonymous$$obile Input menu in the editor.
Your answer
Follow this Question
Related Questions
WINDOWS APP STORE crashed when building a Universal 10 app 0 Answers
Migrating from Windows Standalone to UWP 0 Answers
Assetbundle for Windows Phone 8.1 Universal - Error: assetbundle.mainAsset is null 0 Answers
Build app package for windows 8.1 with unity 2019 ? 0 Answers
How to fix (NullReferenceException: Object reference not set to an instance of an object) in my case 0 Answers