Why Widgets can't publishing Complications?

I have a widget that I was hopping to use to publish complications, but SDK does not allow me to add publish complications permission. For some reason, it must be an app, not a widget.

Yes, I know they are "super apps" since 4.0, but if I change my widget to be an app, will it stop being a widget on older devices without Glances and devices with API below 4.0?

0 MobileDriveway over 1 year ago in reply to jim_m_58

jim_m_58 said:
The ability to build iq files for things like the f7 ww/apac devices and the device files for the venu2sq devices. Exactly what they do with the iq file problem, I'm not sure.

So, adding 'ComplicationPublisher' permission to widgets will still remain a hack?

0 jim_m_58 over 1 year ago in reply to MobileDriveway

Report it as a bug, but there is a work-around. Just add

<iq:uses-permission id="ComplicationPublisher"/>

to the manifest.xml yourself. I don't plan on putting a publisher in the app store for a while yet. When Garmin fixes the things I mentioned, I want to do more testing. especially on devices that can't publish.

0 MobileDriveway over 1 year ago in reply to jim_m_58

The bug is that UI does not allow adding this permission to Widget apps.

But I agree - sounds like we need to wait before publishing publishers

0 pstoppani over 1 year ago in reply to MobileDriveway

There are a lot of very serious issues in 4.2.1. Depending on the widget, it can be impossible to build for older devices do the a much larger (4K+) memory foot print for glances. There are several showstopper build iq issues as Jim mentioned. I'd say 4.2.1 is a beta build. Definitely not ready for prime time. Unfortunately, there is no way to go back to 4.1 either. So, we wait for an updated SDK ...

0 jim_m_58 over 1 year ago in reply to pstoppani

I'm not seeing the 4k issue at all, and it sounds like psx tracked it down to something with scoping resources. I've tested my publisher on most of the devices I support in the sim (the venu2sq/m are the exception) and on both devices that handle complications and those that don't.

0 pstoppani over 1 year ago in reply to jim_m_58

Note that the same memory footprint issue affects background processing as well. I see 2K less available in the background in 4.2.1 :( I agree with psx that it has to do with string resources. I'm guessing is that they are not honoring the scope= correctly so that when you use it, it actually includes all strings. My widget has 76 strings, only 12 have scope="glance".

0 _psx_ over 1 year ago in reply to pstoppani

sensorhistory example has only ONE string

adding scope increasing DATA about 4.5kB (what is in this data? nobody knows, there is not enough resource) so it can influence for whole app also background (maybe half of this because you have mentioned about 2kB)