MBTILES not visible when minzoom level not set to 0

[Jnb2387]

What is the bug or the crash?

Vector mbtiles do not show up in map when minzoom is not 0.

Steps to reproduce the issue

I created mbtiles using both GDAL and Tippecanoe and can not get the point features to show up in the map unless I leave the minzoom blank or specify a minzoom of 0.

--Does not work, can not see point features
ogr2ogr -f MVT ogrtest.mbtiles -dsco MAXZOOM=14 -dsco MINZOOM=4 test_points.fgb

--Works, features are visible in the map
ogr2ogr -f MVT ogrtest.mbtiles -dsco MAXZOOM=14 -dsco MINZOOM=0 test_points.fgb

--Does not work, can not see point features
tippecanoe -f -o tippecanoetest.mbtiles -Z4 -z14 -P test_points.json

--Works, features are visible
tippecanoe -f -o tippecanoetest.mbtiles -z14 -P test_points.json

I tried to manual set the zoom levels by right clicking the mbtiles in the Browser and add Min. Zoom Level 4 and Max. Zoom Level 14 and still have issues.

If I create a xyz directory of tiles with min zoom specified and add the connection it works just fine (As long as I have --no-tile-compression flag).

Versions

Tried both 3.26 and 3.24

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

I am using windows 10.

[gioman]

Confirmed here too.

[matsamentet]

Confirmed this issue in QGIS 3.28.3 as well

[alexbruy]

Can't reproduce with the latest master (4178ace) and MBTiles file created with GDAL 3.6.4. Is this still an issue?

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.