nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to Open Map "Invalid call with current token type"

KristalMclean

Collector for ArcGIS on iPad

Trying to open existing map created in ArcGIS Online. Using a global account to log in to Collector for ArcGIS and am not able to load map. Tested the same map using Collector Classic and have no issues loading the map. I have tested loading different maps created the same way and have had no issues loading them in Collector for ArcGIS. I have checked and updated sharing permissions and nothing has been changed on the ArcGIS Online side of things that would usually prevent a map from loading properly.

What am I missing? Thoughts?

Encontre mais publicações marcadas com

Accepted answers

All comments

EmilySpeck

For the map we are currently using, we had the same issue. Found out the feature points that are on the map were the issue. I found what I had to do was save the feature points as a layer. That seemed to solve the issue. Map is currently able to load on all mobile devices.

bfausel

This solution worked for me. Anyone still trapped on Collector should try adding directly from "Add Layer from Web - Service URL."

MJBiazar

Hi @TanyaBagley-Online,

I'm sorry to hear that you are still experiencing this issue. This error may have other causes. However, in order to rule out the wrong date format, can you make sure that all date fields in your feature layer has the proper format? Also, you can try the following:

Create a new map from the same feature layer.
Publish your data as a new feature service.
In the new layer published in step 2, you can remove fields one at a time and re-save your map to see if the issue is caused by any of your fields.

If possible, please share your data with me so I can run some more testing on my end.

All the best,

TanyaBagley-Online

I have tried your solution and it still does not work for me.

So frustrating.

MJBiazar

Hi @JamesReed2 ,

I'm not sure if it gets fixed in the coming update of the Field Maps app but in the meantime, you can work around this issue by changing the date format.

If you don't mind, can you please share more details about how you originally published your data. We are trying to identify the source of the date fields with this format.

Thanks,

JamesReed2

Will the app be updated to resolve this issue?

MJBiazar

Hi @KristalMclean ,

Although this is an old post but since other users has reported the same issue, I wanted to share an update here that may help identifying the issue.

If you have a date field with certain formats in the pop up for a layer in your web map, you may get an error ('invalid call with current token type') when trying to open the map in New Collector and Field Maps while it works fine in Collector Classic.

One example is the following format:

"datePattern": "MMMM d, y"

You can check the format of your date fields in the pop ups by looking at the JSON for the web map using AGO Assistant. If you saw a format like what mentioned above, you can change it to "dateFormat": "shortDateLongTime" to resolve the issue.

Alternatively, you can pen popup configuration > Configure Attributes > change the display format for your date field and save the map.

A bug has been logged against this behavior:

Synopsis: Opening a web map in new Collector and Field Maps app fails with error 'invalid call with current token type' when the map contains a layer with a date field with a date format "datePattern": "MMMM d, y"

All the best,

Anonymous User

I also experienced this issue today. I am running the latest versions of iOS 13.6 on an iPhone 11, Collector for ArcGIS v20.2.2 build 2847, and ArcGIS Field Maps v20.1.0 build 61.

Below are the events that caused and fixed this bug in my scenario in hopes that this may help someone with the same issue in the future:

Yesterday: The web map opened in Collector for ArcGIS (iOS) normally
Today: I edited the popup configuration of three editable hosted feature layers
Today: The web map would not open in Collector for ArcGIS (iOS) or the Field Maps for ArcGIS beta (iOS) and gave the error message 'Unable to Open Map "invalid call with current token type"'
- I checked the Logs (Profile > Troubleshooting > Logs) and each time I tried to open the map this log was recorded: "[OFFLINE] Current user's map folder: my.username@organizationID"
Today: I edited the web map to remove all existing layers and readd them using their Service URLs in the "Add Layer from Web" workflow instead of readding them by browsing ArcGIS Online content in the "Search for Layers" workflow
Today: The web map opened successfully in Collector for ArcGIS (iOS) or the Field Maps for ArcGIS beta (iOS)
Today: I edited the popup configuration of three editable hosted feature layers (added via URLs)
Today: The web map still opened successfully in Collector for ArcGIS (iOS) or the Field Maps for ArcGIS beta (iOS)

So this bug unfortunately still seems to be present in the current versions of these softwares.

JamieLambert

Hi Brent,

Thanks for the info. Once i made a copy of the feature in the web map and deleted the original feature, it was all good. Sounds like it just got a bit out of whack when i changed the pop-up settings. The issue is already resolved for me. Just a bit hairy for a moment there as i have people in the field using that map. We are using Explorer on iOS.

Thanks,

Jamie.

BrentPierce

Jamie,

Sorry you are having issues here. You are getting this error because the Runtime, which both Explorer and Collector are built with, is having trouble opening/parsing the webmap. This could happen for a number of different reasons, but usually involves something unexpected in the JSON of the webmap itself. Is there any way you can share the webmap with us? Also what platform (iOS, Android or Windows )are you using Explorer on?

Thanks,

-Brent

JamieLambert

The original post is from late 2018 and this is still an issue in 2020 for ArcGIS Online. Its not a specific issue for Collector or Explorer as it seems to impact both mobile apps, based on all the comments.

I am having this issue with a map in Explorer. I configured a pop-up and can no longer access the map in Explorer. I get this message " unable to open map "invalid call with current token type" ". This is not a new map and the audience has been using it for a few weeks without issue. Just happened when I configured the pop-up. I am seeing this issue as the content owner.

I made a copy of the feature (in the Web Map) and deleted the original and everything seems to work fine now. I can configure the pop-up and see the results in Explorer.

This behavior seems a little buggy. Any thoughts from Esri staff?

Thanks,

Jamie.

MattMulder

I don't know if anyone's come up with a concrete solution to this issue, but the work-around solution that I've come across is adding the feature layer directly from the Service URL via the "Add Layer From Web" Option

AaronCraig2

Very interesting. I have the World Imagery layer in my maps as well.

AdaLi1

I had the 'Unable to Open Map "Invalid call with current token type"' message when I tried to open my map on Explorer. Deleting World Imagery Wayback layers (https://www.arcgis.com/home/group.html?id=0f3189e1d1414edfad860b697b7d8311#overview) from my map did the trick. I'm not sure what it was exactly from these layers that caused the issue.

ElizabethZizzamia1

Has anyone figured out a solution to this problem? I'm the admin for a large organization that produces many web maps used for data collection in Collector. Only some of the web maps have the issue of -working perfectly in Classic but won't open in new Collector and shows the token error. The new version of Collector is so much better I'd prefer never to use Classic. It gets confusing for the users who may need to download 2 separate apps just to collect data. The web map that I'm currently working on only has one layer and was created spring of this year so it's not particularly old.

Anonymous User

I noticed that as well with the configure attributes. I did find that it seemed to be occurring with views and trying to make copies of the views. ultimately, as amber converse pointed out. I went back to older sources of data and recreated the maps with joins for the newer data, so far haven't had any of the same issues and I've isolated and marked those layers so no one uses them.

KristalMclean

Quick follow up. Another issue I have discovered is that it will not display properly if you try and configure the attributes of a view using the 'Configure Attributes' function that is in the Configure Pop up window.

I tried to configure a few attributes in a view so that they were view only. Once I configured that attribute within the map I received the "Invalid Token" message when I tried to open the updated map in Explorer or Collector for ArcGIS.

KristalMclean

So, this is the odd behaviour I just came across while trying to open an existing map using the Explorer app. I received the "Invalid Token" message when I was trying to open one existing map but not for a different map created during the same time period last year.

Here is what I've figured out, it doesn't like a copy of a view, or at first glance that seems to be a basic assessment of what might be part of the issue.

When the map contained a feature layer (hosted, view) there were no issues opening the map up in Collector for ArcGIS or Explorer.

BUT if I made a copy of that view in the map so that I could have multiple versions of the same feature layer to symbolize the data differently based on filters, the map does not load and I receive the "invalid token" message. I did not change any sharing permissions.

By removing the copy of the layer but keeping the original feature layer (hosted, view) I was able to get the map to load correctly.

That's the "fix" I've managed to find.

AmberConverse

We experienced this same issue (and saw the same error) using Collector. We originally published the data for use in the new Collector, and everything appeared to be working fine. However, in the last stages before sending folks into the field, we added a new field to the hosted feature layer. At this point, the layer stopped working in the new Collector, and eventually, the entire map just failed to load . We were able to open things and edit features using the classic/old Collector.

Ultimately, we republished the dataset from the original source data (adding in the new field prior to publishing). Everything now works in the new version of Collector.

Anonymous User

I went back to my original data (spreadsheets with x/y for point features) and recreated the feature, map, and relationships (we use related tables) and some of the views and it works fine. the only difference is i didn't add the attachments, so:

1. either the attachments are throwing it off

2. I created all the other maps/views during a time of a very different build for Collector (Beta name: Aurora) that can no longer understand them and since Classic hasn't been changed really, that's probably why it still works in Classic?

Sidenote: I also found out that none of the views i made during that time will work for offline collection, of any sort (ad hoc/pre-planned), so in our rural areas, its basically useless right now.

AaronCraig2

Just started seeing this behavior in Collector now with a map that was working. Same map is working in classic.

I did add views to the map, I suspect Aurora does not like hosted feature service view layers...

Anonymous User

Same thing as many of you. Created a new view from the exact same Feature Layer (Hosted) that I use on several other occasions and at first, it wouldn't open the map with an prompt "Invalid token". Then eventually it did work... kinda. you couldn't click on the features or access them in any way in Collector.

..aaaaand it all works perfectly in Classic. I wish this wasn't happening before data collection season this week, but at least we still have classic

JoeBryant1

We're getting the same behavior - no longer able to open a shared map in Collector that hasn't had sharing changed. We also noticed that we can't select and edit collected points in the map.

We had been using the new version of Collector for iOS, and Collector Classic on Android, and it was working in iOS but had the known issues in Android. We downloaded Collector Beta for Android and began testing that around the time these error began.

If anyone solves this - please post!

JoelCarranza2

I had a similar scenario, however, in my case, the map was working just fine until I configured the pop-up contents. Very weird. I wish I could leave the pop-up contents unchanged so that we could use the new app.

deleted-user-jxpbpbjlZInj

So - My issue seemed to be somewhere in a Feature Class that was derived from Survey123. I took it out and then re-added it (as is) and it seemed to resolve the issue.

HOWEVER, then I was unable to click on the resulting S123 points in Collector to edit them (even though they were enabled for editing.) BUT, I could add a point straight from Collector. YET - the questions from S123 were showing up as barcode scan fields!

So now I have more questions than answers. I did talk to ESRI about it and they were unable to figure out the issue. I've updated them as well on these recent "findings"

MarisaClaggett

As Collector Aurora is fairly new, I would highly recommend creating a case with Esri Technical Support so that they can investigate this error.

Esri Support Contact Support

deleted-user-jxpbpbjlZInj

Were you able to figure this out? We're also having the same issue. Additionally, we aren't able to download the pre-defined map areas. I've gone through documentation and I don't see any reason why these areas are unable to download.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.