Got the error: Invalid argument. Only uncompressed packages are supported.

[qmjy]

        this.tileCache = new TileCache(tpk.getAbsolutePath());
        this.tileCache.loadAsync();
        this.tileCache.addDoneLoadingListener(() -> {
            if (tileCache.getLoadStatus() == LoadStatus.LOADED) {
                if (loadMetadata()) {
                    this.valid = true;
                }
            } else if (tileCache.getLoadStatus() == LoadStatus.FAILED_TO_LOAD) {
                ArcGISRuntimeException error = tileCache.getLoadError();
                if (error != null) {
                    logger.error("{} 加载失败原因: {}", tpk.getName(), error.getMessage());
                } else {
                    logger.error("加载失败，但未捕获到具体的错误对象。");
                }
            } else {
                logger.error("Load tpk failed: {}", tpk.getAbsolutePath());
            }
            this.loaded = true;
        });

can not read compact tpk, only support for compact_v2 ?

[mbcoder]

@qmjy you should know that the ArcGIS Maps SDK for Java is deprecated so I'd discourage you from using this SDK. Please see this notice for more information. There are alternatives here: https://developers.arcgis.com/

As for support of tile packages the doc says:

Tile package (.tpk, .tpkx) - a tile cache of data, packaged into one convenient, portable file, ideal for offline sharing of complete tiled layers in a disconnected environment or via a portal.

Compact Cache - a directory structure where groups of tiles are combined into larger .bundle files, preserving performance and reducing copy times and the size on disk of the cache.

Exploded Cache - a directory structure where map tiles are stored as individual files.

Can you tell me how the tile package you are using was created?

[qmjy]

@mbcoder First of all, thank you very much for your response. I obtained a.tpk file from the customer, and I only know that its format is quite old. When I tried to parse it using the ArcGIS Map SDK for Java, the aforementioned error occurred. However, if I re-export the.tpk file using the latest ArcGIS Pro and then parse it, it works fine. Therefore, I'm not entirely sure what the issue with the original.tpk file might be.