• State Verified Answer
  • Replies 17 replies
  • Subscribers 20 subscribers
  • Views 1208 views
  • Users 0 members are here
Options
Related

The products and setting resources declared in the manifest file must match the app file directory structure

RodolpheDumesnil
2 months ago

Hi all,

I recently switch to VSC (I know I should have done that a while ago!)...

I just export the app, no error, I get the .iq file, but when I try to upload, it is rejected with the following message :

The products and setting resources declared in the manifest file must match the app file directory structure. {0}

Does anyone have any ideas of what I'm doing wrong ?
Note : Sorry for my english, not my native langage

  • 0 2 months ago in reply to RodolpheDumesnil
    RodolpheDumesnil said:
    Sorry if I don't undestand but what is a "preview device", it's a device that I add as a product in my manifest as

    Sorry for not being clear.

    A preview device is a placeholder device released by Garmin to allow devs to test unannounced devices, or upcoming CIQ versions. For example, before venu2 and venu2s were announced, they were released to CIQ devs as wearable2021 and smallwearable2021. Other preview devices literally have "preview" in the name.

    In the past, exporting a project with preview devices selected would cause the export to fail, but now it looks like a warning.

    What doesn't make sense is that the compiler is giving you warnings which say that completely valid part numbers for venu2s are not supported for export [as if they were part of a preview device].

    RodolpheDumesnil said:
    So, thanks for your explanations, so OK the warning is normal, but why it build an iq file that is finally refused by garminIQ ?

    That does seem like a bug.

    To be clear the warnings about vivoactive 3 and delta 2 px are normal, but the last 2 warnings about 006-b3704-00 and 006-b3949-00 are not.

    RodolpheDumesnil said:
    And anyway, what is the good way for me ?
     - Edit the compiler.json and remove the part with connect IQ version 3.0.3 ? It seems to be dangerous, because it could affect some other project...

    No, I think something else is going on here.

    Maybe you should post in the bug reports section and email your project to [email protected] [if you're comfortable in doing so]

  • 0 2 months ago in reply to FlowState

    Oh ! You are right !! I read too quickly these two lines and I associated them with the previous two.

    My apologies Sweat smile

    As you said, I deleted Venu2 and download it again. Export is currently running, but it seems to be good !!
    Many many thanks.

  • 0 2 months ago in reply to RodolpheDumesnil

    Finaly not better.

    I will try some other tests, and post a report if I cannot go ahead.

    Thanks again for your help.

  • +1 2 months ago in reply to RodolpheDumesnil

    RESOLVED
    I tried to find in which file "006-b3704-00" and "006-b3949-00" was, without success.
    I also tried by following the log, to know when compiling wich device the error appears, but it appears at the end ...
    So I remove all files in the folder devices of the SDK and redownload it from SDK manager.

    It OK again now.

  • 0 1 month ago

    I have the same kind of problem using 8.1.1.

    If a add venu3 to the manifest i get these errors.
    78 OUT OF 78 DEVICES BUILT
    WARNING: Device '006-B3704-00' is being ignored by the package tool. It is not supported for export.
    WARNING: Device '006-B3949-00' is being ignored by the package tool. It is not supported for export.
    BUILD SUCCESSFUL

    Somehow the packagers runs into troubles.

    I'll try to reload the devices from the SDK

  • 0 1 month ago in reply to flocsy🤠
    Reijndert said:
    If a add venu3 to the manifest i get these errors.
    78 OUT OF 78 DEVICES BUILT
    WARNING: Device '006-B3704-00' is being ignored by the package tool. It is not supported for export.
    WARNING: Device '006-B3949-00' is being ignored by the package tool. It is not supported for export.
    BUILD SUCCESSFUL
    flocsy🤠 said:
    Those are warnings, not errors

    Those warnings are the point of this thread.

    - OP had the exact same warnings during export and their IQ file was rejected by the store with the following message:

    "The products and setting resources declared in the manifest file must match the app file directory structure"

    - '006-B3704-00' and '006-B3949-00' should be valid part numbers for export (they are 2 part numbers for venu2s), so there's seemingly no reason they should be excluded

    - others can export venu2s without getting those warnings (I don't see them).

    Furthermore:

    - it doesn't make sense that these errors would appear when venu3 is added. (even if venu2s is already in the manifest)

    The real question is whether anyone who sees these *exact* warnings will also have the same problem uploading their app to the store. [And even if they don't have that problem, it's still not a good thing]

    Having said all of that, venu2s actually has 4 part numbers, in this order:

    006-B3704-00: WW (corresponds to worldWidePartNumber)

    006-B3949-00: APAC

    006-B4175-00: WW

    006-B4181-00: APAC

    [All 4 are on CIQ 5.0 and firmware 19.05, according to compiler.json]

    According to the CIQ store's device types API endpoint:

    - the 1st and 2nd part numbers are "normal" venu 2s

    - the 3rd and 4th part numbers are "mercedes-benz" venu 2s

    To me this is further proof that B3704 and B3949 should still be valid part numbers for export. It's not like Garmin suddenly decided that only Mercedes-Benz Venu 2S is valid, and not plain Venu 2S.