I'm not able to open a mobile map package created using ArcGIS Pro 3.4.2 in Field Maps 24.3.0 Build 1133 on iOS. It is reporting "Required client version (13.2) is higher than ArcGIS Runtime supports (13.0).
@WillyLynch3 got my hopes up when they closed their question but it's still an issue with the latest ArcGIS build.
Anyone have any solutions?
Thanks!
Solved! Go to Solution.
@DanielFox1 After digging deeper and rebuilding the mmpk from the ground up adding layer after layer, there was is a single service from AGOL that has asterixes in the date fields, indicating high precision fields. Removing the layer fixed the problem. It's clearly a bug that FM can't handle these fields in an mmpk.
Thanks for flagging this. Do you get any special characters in the data fields such as an asterisk etc
Did this happen at 3.4.0?
Can you rollback to this version?
If you haven't done so I would recommend logging a ticket with your technical support to have this looked into further.
No special characters to my knowledge - there's a lot of layers and a lot of data, but presumably given that it worked fine using ArcGIS Pro 3.1, it's not that. When we upgraded to 3.3.2, field maps started throwing the error. Rolled back to 3.1 and it started working again.
Cut forward to Willy's comment saying it's fixed in 3.4.0, we upgraded to the latest build of 3.4.2, and it broke again. Rolled back to 3.4.1 and still broken. Rolled back to 3.4.0 and it still failed.
@DanielFox1 After digging deeper and rebuilding the mmpk from the ground up adding layer after layer, there was is a single service from AGOL that has asterixes in the date fields, indicating high precision fields. Removing the layer fixed the problem. It's clearly a bug that FM can't handle these fields in an mmpk.
Just tried myself and again see the issue. At AGP 3.4.0 and FM 24.3.0 data with date fields seemed to work. Now with AGP 3.4.2 and FM 24.3.0, the error message about needing required version 13.2 returns. I do not have ability to roll back to 3.4.0 so cannot test if this is patch issue. Hopefully Esri support can troubleshoot your issue. Not critical for me now so will not submit a ticket. Good luck!