Demo App myapp is loading with scrambled screen.

[sutara-aayush]

Steps to Reproduce

Please tell us what you were doing and what went wrong. If you are running flutter tools from the command line, please try adding the -v or --verbose option to gather more information.

If the problem is with your application's rendering, please attach a screenshot and any relevant source code.
If you are getting an exception in the logs, and your code is implicated in the first few frames, then please include the source code for the functions involved.

Logs

Run your application with flutter run and attach all the log output.

Run flutter analyze and attach any output of that command also.

Flutter Doctor

Paste the output of running flutter doctor -v here.

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.

[xqwzts]

Hi @sutara-aayush this seems to be a rendering issue with the emulator, it should be resolved by running in software rendering mode by passing the enable-software-rendering flag to flutter:

flutter run --enable-software-rendering

[sutara-aayush]

Hello, thanks for help @xqwzts i tried this but got something as below.

[sutara-aayush]

But i am able to see the devices using flutter devices

[xqwzts]

I'm not really sure what would be causing that, you're right that the device is detected, from the output we can see that the flutter tool detects the device, builds the apk, and segfaults either while pushing the files to the device or right after that while trying to run the app.

You might try to run in verbose mode:
flutter run --enable-software-rendering -v

Hopefully this will give us a more detailed error log that points to the cause.

[sutara-aayush]

Still its not working sir @xqwzts

[sutara-aayush]

@xqwzts .. sir it started working as I updated to windows 10. Thanks for giving time sir.

[Hixie]

I'm going to close this since it's not blocking you any more and we don't have enough information to fix it.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.