webmap not supported after updating to AppStudio 5.3

[DavidPuckett]

I updated to AppStudio 5.3 and now my map (that was loading in 5.2) is not loading with a task status of LoadStatusFailedToLoad and an error message stating that the map is not supported because it is a version Pre 2.0. But the web map was created just 3 months ago and I saved it today. It is also working in AppStudio 5.2.

Is this a bug or is there something I need to do differently for AppStudio 5.3?

[TrevorFrame]

Hi @DavidPuckett,

I was able to reproduce the issue with your web map you provided, so thank you for doing that. I did what @rob_hewy recommended and made an exact copy of your map using the new map viewer and the web map copy is working on my end. Hopefully, this simple fix works for you.

Best,

Trevor Frame

[DavidPuckett]

Ok this is most certainly a bug in 5.3. I narrowed it down to a drop shadow in one of the layers. I removed the 'effect', as they are referred to in the json, and the map worked (no incompatible version error) in all 5.3 environments. Here's the json I removed if it's helpful:

"effect": [
                {
                    "scale": 47464.25105939465,
                    "value": [
                        {
                            "type": "drop-shadow",
                            "xoffset": 0.75,
                            "yoffset": 0.75,
                            "blurRadius": 0.375,
                            "color": [
                                115,
                                114,
                                114,
                                255
                            ]
                        }
                    ]
                },
                {
                    "scale": 11866.062764848662,
                    "value": [
                        {
                            "type": "drop-shadow",
                            "xoffset": 1.5,
                            "yoffset": 1.5,
                            "blurRadius": 0.75,
                            "color": [
                                115,
                                114,
                                114,
                                255
                            ]
                        }
                    ]
                },
                {
                    "scale": 2966.5156912121656,
                    "value": [
                        {
                            "type": "drop-shadow",
                            "xoffset": 3,
                            "yoffset": 3,
                            "blurRadius": 1.5,
                            "color": [
                                115,
                                114,
                                114,
                                255
                            ]
                        }
                    ]
                }
            ],

[rob_hewy]

Just so you know the map is now reporting the version below:

qml: ==================== GIST 8010 ==================
qml: ===== Version: 2.24
qml: ==================== WAR  END  ==================

The map I tested was:

"https://seattlecitygis.maps.arcgis.com/home/item.html?id=d5e2a56846c94ec685a334010987016b"

[DavidPuckett]

Yes I saw that, but there's no way it is an issue with the version number. If I put the drop shadow effect back in it breaks. Very reproducible.

[rob_hewy]

Is this an effect that the mapviewer adds to the layer? if so, I will try to break one of my maps

[rob_hewy]

Layer effects definitely blows up the map; Knocks-out the version number

I only tested drop shadow.  UPDATE: Bloom causes problems too.

qml: ==================== GIST 8010 ==================
qml: ===== Version: 
qml: ==================== WAR  END  ==================
qml: 

[rob_hewy]

Turn the effect off then save and the map works again:

qml: ==================== GIST 8010 ==================
qml: ===== Version: 2.24
qml: ==================== WAR  END  ==================
qml: 

[rob_hewy]

Could be a runtime issue 100.12 versus 100.13.

A software regression?

[rob_hewy]

Simple app below that isolates the problem to the Map QML type (map version is 2.23/2.24):

import QtQuick 2.13
import QtQuick.Controls 2.13

import ArcGIS.AppFramework 1.0
import Esri.ArcGISRuntime 100.13

App {
    id: app
    width: 400
    height: 640

    // ==============================================================================================
    // 'https://seattlecitygis.maps.arcgis.com/home/item.html?id=d5e2a56846c94ec685a334010987016b'
    //
    // no effects
    // https://bcitgis.maps.arcgis.com/home/item.html?id=0a5459e98e15445b8ba8392f834a1c2b
    //
    // with an effect
    // 'https://bcitgis.maps.arcgis.com/home/item.html?id=d5db1d15460d41379dfcd0f66cddaaa9'
    // ==============================================================================================

    MapView{
        id: mapView
        anchors.fill: parent
        Map{
            id: map
            onErrorChanged: log()
            initUrl: 'https://bcitgis.maps.arcgis.com/home/item.html?id=d5db1d15460d41379dfcd0f66cddaaa9'
        }
    }
    function log(){
        console.log('=========================================')
        console.log(`===== ${map.error.message}`)
        console.log('=========================================')
        console.log('=========================================')
        console.log(`===== ${map.error.additionalMessage}`)
        console.log('=========================================')
    }
}

[TrevorFrame]

Thank you both, @DavidPuckett @rob_hewy , for bringing this to our attention and for your thoroughness. We will research this more and address this issue. 

Update: This will be address in the next AppStudio 5.4 update with the new ArcGIS Runtime 100.14. In the mean time, please remove any layer effects you have in your web map when using AppStudio 5.3.