Acknowledged
5 months ago

Problem with installing app

One of my user has tried to install widget PSX-7 (https://apps.garmin.com/apps/1944b8b4-409e-482d-b7b3-becd4e8b1b05) but he couldn't due the incapability error but he has installed PSX-6 (https://apps.garmin.com/apps/e4ce9423-c37e-4aa7-b778-f24c2347c923). Both are built the same SDK (7.3.1m PSX-7 few days later), both have the same min API level to 2.4.

_psx_
Parents
  • 6 months ago

    > I I'm not sure but probably PSX-6 hss subset of device from PSX-7

    You can be sure because I already posted the diff of the compatibleDevicePartNumbers arrays: some part numbers are unique to PSX-6 and some are unique to PSX-7, while most part numbers are common to both. If by "device" you actually mean CIQ device and not part number, you can obviously compare manifest.xml for each app to be sure.

    > BTW

    > Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira 010-02564-03

    > There is no *2564* nowhere

    I have no idea what you're quoting here: "Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira 010-02564-03". Yes, that's apparently an Instinct 2S hardware variant you can (or could) buy, but what's the relevance to your app?

    You can see that format of the part number (010-02564-03) is different than the part numbers that appear in CIQ compiler.json as partNumbers[].number. 010-02564-03 looks like a part number that would appear on a store box (used by retailers) - it also looks like various hardwarePartNumber values in compiler.json

    010-02564-03: (looks like) hardwarePartNumber (note that there's one of these for 1 CIQ device's compiler.json)

    006-B3889-00: (looks like) partNumbers[].number (there can be several of these for 1 CIQ device's compiler.json)

    Notice how every partNumbers[].number in compiler.json starts with "006-B"? While every hardwarePartNumber starts with "010-0"? 2 completely different patterns. Retailers also never seem to use the "006-B" part numbers.

    I agree that "010-02564-03" (or any string containing "2564") doesn't appear as a hardwarePartNumber, but then again "Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira" (or just "Ericeira" doesn't appear as part of a device display name or a name in the device types request.

    Similarly, on the Garmin Instinct 2* page, there's all kinds of different (hardware) part numbers for various combos of colours and variants (standard vs. tactical vs. camo):

    https://www.garmin.com/en-CA/p/775357/

    Just to name 2:

    010-02626-13 - Instinct® 2 - Camo Edition (Graphite Camo)

    010-02805-11 - Instinct® 2X Solar (Flame Red)

    Most of those (hardware) part numbers don't appear in any CIQ-related contexts (like compiler.json or the deviceTypes request used by the store) because CIQ doesn't care what colour your watch is or whether it's a camo edition.

    For reference, the CIQ hardwarePartNumber for...

    ... Instinc 2 is 010-02626-10

    ... Instinct2X is 010-02805-10

    > All the seme, apart from the app type and user can download watch face but can't widget.

    Yeah it's a weird problem. When you export the IQ file for each app, do you get any warnings about excluded part numbers?

Comment
  • 6 months ago

    > I I'm not sure but probably PSX-6 hss subset of device from PSX-7

    You can be sure because I already posted the diff of the compatibleDevicePartNumbers arrays: some part numbers are unique to PSX-6 and some are unique to PSX-7, while most part numbers are common to both. If by "device" you actually mean CIQ device and not part number, you can obviously compare manifest.xml for each app to be sure.

    > BTW

    > Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira 010-02564-03

    > There is no *2564* nowhere

    I have no idea what you're quoting here: "Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira 010-02564-03". Yes, that's apparently an Instinct 2S hardware variant you can (or could) buy, but what's the relevance to your app?

    You can see that format of the part number (010-02564-03) is different than the part numbers that appear in CIQ compiler.json as partNumbers[].number. 010-02564-03 looks like a part number that would appear on a store box (used by retailers) - it also looks like various hardwarePartNumber values in compiler.json

    010-02564-03: (looks like) hardwarePartNumber (note that there's one of these for 1 CIQ device's compiler.json)

    006-B3889-00: (looks like) partNumbers[].number (there can be several of these for 1 CIQ device's compiler.json)

    Notice how every partNumbers[].number in compiler.json starts with "006-B"? While every hardwarePartNumber starts with "010-0"? 2 completely different patterns. Retailers also never seem to use the "006-B" part numbers.

    I agree that "010-02564-03" (or any string containing "2564") doesn't appear as a hardwarePartNumber, but then again "Instinct® 2S Solar – Surf Edition, Surf Edition, Ericeira" (or just "Ericeira" doesn't appear as part of a device display name or a name in the device types request.

    Similarly, on the Garmin Instinct 2* page, there's all kinds of different (hardware) part numbers for various combos of colours and variants (standard vs. tactical vs. camo):

    https://www.garmin.com/en-CA/p/775357/

    Just to name 2:

    010-02626-13 - Instinct® 2 - Camo Edition (Graphite Camo)

    010-02805-11 - Instinct® 2X Solar (Flame Red)

    Most of those (hardware) part numbers don't appear in any CIQ-related contexts (like compiler.json or the deviceTypes request used by the store) because CIQ doesn't care what colour your watch is or whether it's a camo edition.

    For reference, the CIQ hardwarePartNumber for...

    ... Instinc 2 is 010-02626-10

    ... Instinct2X is 010-02805-10

    > All the seme, apart from the app type and user can download watch face but can't widget.

    Yeah it's a weird problem. When you export the IQ file for each app, do you get any warnings about excluded part numbers?

Children
No Data