Acknowledged
5 months ago

The sample projects Toasts and Selectable are broken in 4.2.0-beta2

% cd $sdk420/samples/Selectable
% "$sdk420/bin/monkeyc" "-o" "bin/Selectable.prg" "-f" monkey.jungle "-y" "$developer_key" "-w" "-l" "1" "-d" "approachs60"
WARNING: approachs60: The launcher icon (16x16) isn't compatible with the specified launcher icon size of the device 'approachs60' (40x33). Image will be scaled to the target size.
ERROR: approachs60: Could not resolve /images/back_default.png
ERROR: approachs60: Could not resolve /images/back_pressed.png
ERROR: approachs60: Could not resolve /images/menu_default.png
ERROR: approachs60: Could not resolve /images/menu_pressed.png
ERROR: approachs60: An undefined resource reference was detected during resource processing: @Drawables.DefaultBackButton.
ERROR: approachs60: An undefined resource reference was detected during resource processing: @Drawables.PressedBackButton.
ERROR: approachs60: An undefined resource reference was detected during resource processing: @Drawables.DefaultMenuButton.
ERROR: approachs60: An undefined resource reference was detected during resource processing: @Drawables.PressedMenuButton.

But if I compile it (the same project, taken from the 4.2.0beta2 samples) with 4.1.7 the compilation succeeds, and I can run the resulting program. So this is probably a bug in 4.2.0 (unless there's a subtle bug in the project that earlier compilers simply didn't notice).

For Toasts, I get

% cd $sdk420/samples/Toasts
% "$sdk420/bin/monkeyc" "-o" "bin/Toasts.prg" "-f" monkey.jungle "-y" "$developer_key" "-w" "-l" "1" "-d" "fenix7"
ERROR: Device 'fenix7' does not support API Level '4.2.0'.

And this time 4.1.7 agrees. So in this case it looks like the sample project needs fixing.

markw65
Parents
  • over 2 years ago

    For toasts, the error you see is valid for the fenix7 right now.  As far as the sim and devices goes, the fenix7 is at 4.1.x, and you need to use the fenix7system6preview device instead which is 4.2.0.  Also, you want to use the 4.2.0 beta 2 SDK, and not a 4.1.x SDK.

    Then there is a typo in the manifest.xml, where for entry, it has "ToasterApp" and that needs to be changed to match the app.mc "ToastsApp"

    Using the system6preivew device (this is system 6 functionality) and correcting the typo, it runs in the sim:

Comment
  • over 2 years ago

    For toasts, the error you see is valid for the fenix7 right now.  As far as the sim and devices goes, the fenix7 is at 4.1.x, and you need to use the fenix7system6preview device instead which is 4.2.0.  Also, you want to use the 4.2.0 beta 2 SDK, and not a 4.1.x SDK.

    Then there is a typo in the manifest.xml, where for entry, it has "ToasterApp" and that needs to be changed to match the app.mc "ToastsApp"

    Using the system6preivew device (this is system 6 functionality) and correcting the typo, it runs in the sim:

Children
  • over 2 years ago in reply to _psx_

    With the fenix7 vs fenix7system6preivew, it's probably just a timing thing.  There is alpha FW for the f7 with system6, but until there is production FW with that, devices for the SDK won't have that version.  Same with other devices like the fr255,955, and v2.

    The typo in the manifest could just be a fix didn't make it into the beta2 build (new sample. beta SDK, etc) but it's a pretty minor fix and the error message points you right to it.  That said, it should be fixed but could take some time until there is another update to the SDK (beta1 was mid Oct, beta2, mid Jan)

    I've not tried it, but I kind of doubt this can be used in watch faces.  The doc doesn't say.

  • over 2 years ago in reply to jim_m_58

    So, it does mean nobody try to compile app as entry is bad?

    btw.  Can watch faces use toasts?