This seems to be happening because Edge 1030 APAC (Asia-Pacific) devices only support 3.1.3. APAC firmware updates typically lag behind ROW (rest of the world).

You can see this if you look in the device library (i.e. on Windows: %APPDATA%\Garmin\ConnectIQ\Devices\edge1030\compiler.json) and search for the part number in question.

I would be surprised if it were skipping *all* devices, though.

Thanks FlowState and Jim, all skipped devices could be APAC versions.

However, I am dealing with this because of an error uploading the app to IQ store.

There were no compatible devices found for the part numbers declared in the manifest file. 006-B4175-00

I do not know how to find which device corresponds to this ID if I do not open every compile.json file, but no warning related to this device is printed during building process.

I have also unpacked the *.iq file and confirmed that folder 006-B4175-00 exists.

Your min API is 3.2 and the apac version is 3.1, so it's rejected by the app store as it doesn't meet the min api.  

But this is a datafield already uploaded to the store. I have no experienced this issue for any of the previous versions, only today uploading an update the store does not validate it.

I have always set minimum API to 3.2, and build for the same list of devices. I have not done any modification since initial version. What device corresponds to 006-B4175-00?

        <iq:products>
            <iq:product id="edge1030"/>
            <iq:product id="edge1030bontrager"/>
            <iq:product id="edge1030plus"/>
            <iq:product id="edge530"/>
            <iq:product id="edge830"/>
            <iq:product id="fenix5plus"/>
            <iq:product id="fenix5splus"/>
            <iq:product id="fenix5xplus"/>
            <iq:product id="fenix6pro"/>
            <iq:product id="fenix6spro"/>
            <iq:product id="fenix6xpro"/>
            <iq:product id="fr245m"/>
            <iq:product id="fr645m"/>
            <iq:product id="fr745"/>
            <iq:product id="fr945"/>
            <iq:product id="marqadventurer"/>
            <iq:product id="marqathlete"/>
            <iq:product id="marqaviator"/>
            <iq:product id="marqcaptain"/>
            <iq:product id="marqcommander"/>
            <iq:product id="marqdriver"/>
            <iq:product id="marqexpedition"/>
            <iq:product id="marqgolfer"/>
            <iq:product id="venu2"/>
            <iq:product id="venu2s"/>
        </iq:products>

It's the APAC version of the edge 1030.  It could be you updated your devices and this one is new.

Look at the manifest.xml that's within the iq file

Thanks for the advice. 006-B4175-00 is not edge 1030, but Venu2S. I have removed it from build targets and same happens for 006-B4171-00 (Venu2). Removing both, all works fine and I have been able to upload the datafield seamlessly.

Strange, because as I have mentioned before, folder for both devices was present inside the iq package and both support version 4.0

Maybe some wrong information about these devices. SDK manager downloaded an update for both some days ago

You're right, 006-B4171-00 and 006-B4171-00 are new part numbers. I haven't updated my devices and in a while and those part numbers did not exist in my copy of the device library until I downloaded the latest update.

Interestingly, I noticed that the information for the new part numbers lacks firmwareVersion, which is present for most (but not all) other part number entries.