You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
404 on network_service.mojom.dart, url_loader.mojom.dart and service_registry.mojom.dart #27
$ ./packages/sky/sky_tool start
Dart VM version: 1.11.1 (Thu Jul 2 05:10:33 2015) on "macos_x64"
error: device not found
/Users/johnmccutchan/workspace/sky_test/main.dart does not exist.
$ touch main.dart
$ ./packages/sky/sky_tool start
Dart VM version: 1.11.1 (Thu Jul 2 05:10:33 2015) on "macos_x64"
error: device not found
error: device not found
Traceback (most recent call last):
File "./packages/sky/sky_tool", line 310, in
SkyShellRunner().main()
File "./packages/sky/sky_tool", line 303, in main
exit_code = args.func(args, pids)
File "./packages/sky/sky_tool", line 160, in run
if not self._is_package_installed(ANDROID_PACKAGE):
File "./packages/sky/sky_tool", line 127, in _is_package_installed
return subprocess.check_output(pm_path_cmd).strip() != ''
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 573, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['adb', 'shell', 'pm', 'path', 'org.domokit.sky.demo']' returned non-zero exit status 255
I still get a black screen on the Hello World example but that should not be related to this issue. I get the black screen on a fresh install of the SkyDemo from the App store too. (Nexus 7, Android 5.1.1), any thoughts on where to look for the root cause?
It probably is black text on a black background. When we moved from the old world (.sky) to the new world (.dart) we changed the default background color from white to black to avoid the flash-of-white problem that the Web had for years during the load of pages.
I suspect we need to update hello_world to set a text color:
I think that we changed the default text color to white last week. In the current world, though, hello_world draws its text under the status bar, which can make it hard to notice. Do you see that text when you run hello_world on your device?
@eseidel@iansf Thanks for the hints. It was both a black-on-black and under-the-statusbar issue. Putting it in a container with light background, I can see the text just fine now. ( I was creating my own hello world based on the code in README rather than trying the examples/hello_world so the text is still black )
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.
Activity
eseidel commentedon Jul 6, 2015
It sounds like pub run sky:init wasn't run (which calls pub run momom:generate). ./packages/sky/sky_tool should do that for you however.
I can attempt to reproduce when I'm in the office. I suspect I failed to publish the latest Sky package correctly. @johnmccutchan
johnmccutchan commentedon Jul 6, 2015
On a clean sky_test project:
$ ./packages/sky/sky_tool start
Dart VM version: 1.11.1 (Thu Jul 2 05:10:33 2015) on "macos_x64"
error: device not found
/Users/johnmccutchan/workspace/sky_test/main.dart does not exist.
$ touch main.dart
$ ./packages/sky/sky_tool start
Dart VM version: 1.11.1 (Thu Jul 2 05:10:33 2015) on "macos_x64"
error: device not found
error: device not found
Traceback (most recent call last):
File "./packages/sky/sky_tool", line 310, in
SkyShellRunner().main()
File "./packages/sky/sky_tool", line 303, in main
exit_code = args.func(args, pids)
File "./packages/sky/sky_tool", line 160, in run
if not self._is_package_installed(ANDROID_PACKAGE):
File "./packages/sky/sky_tool", line 127, in _is_package_installed
return subprocess.check_output(pm_path_cmd).strip() != ''
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 573, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['adb', 'shell', 'pm', 'path', 'org.domokit.sky.demo']' returned non-zero exit status 255
After attaching a device I see what's going on.
johnmccutchan commentedon Jul 6, 2015
This should be fixed in https://codereview.chromium.org/1224623007/
johnmccutchan commentedon Jul 6, 2015
@aghassemi Until the next revision of the Sky SDK a work around is:
aghassemi commentedon Jul 6, 2015
Thanks @johnmccutchan Workaround fixed the 404s.
I still get a black screen on the Hello World example but that should not be related to this issue. I get the black screen on a fresh install of the SkyDemo from the App store too. (Nexus 7, Android 5.1.1), any thoughts on where to look for the root cause?
eseidelGoogle commentedon Jul 6, 2015
It probably is black text on a black background. When we moved from the old world (.sky) to the new world (.dart) we changed the default background color from white to black to avoid the flash-of-white problem that the Web had for years during the load of pages.
I suspect we need to update hello_world to set a text color:
https://github.com/domokit/mojo/tree/master/sky/sdk/example/hello_world
iansf commentedon Jul 6, 2015
I think that we changed the default text color to white last week. In the current world, though, hello_world draws its text under the status bar, which can make it hard to notice. Do you see that text when you run hello_world on your device?
aghassemi commentedon Jul 7, 2015
@eseidel @iansf Thanks for the hints. It was both a black-on-black and under-the-statusbar issue. Putting it in a container with light background, I can see the text just fine now. ( I was creating my own hello world based on the code in README rather than trying the examples/hello_world so the text is still black )
Use the NDK at API level 16 for backward compatibility with Jellybean (…
github-actions commentedon Sep 7, 2021
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 -vand a minimal reproduction of the issue.