This post tracks existing and historical known issues affecting GeoBIM. It’s updated regularly to help you stay informed and avoid duplicate reports.
Date Identified (Software Release) | Title | Description | Status | Bug ID (if applicable) |
02/18/2026 (AGOL2026.R1) | Revit 2026 models are not supported for GeoBIM's 3D Models layer output | The Add Document Models tool returns errors for Revit 2026 models as they are not currently supported. When this happens, the error log will list the failure with the message Exception: No 3D model available. | Bug identified | |
01/23/2026 (AGOL2026.R1) | IFC models fail to ingest to GeoBIM when output spatial reference (SR) is set to WKID 3857 | Some IFC models will fail to ingest to GeoBIM when the output SR is set to WKID 3857 (WGS 1984 Web Mercator Auxiliary Sphere). This occurs when the IFC model does not have internal coordinates defined in the IfcMapConversion entity, but does include a .prj and .wld3 file. Workaround: Use a different SR output | Bug identified | |
12/01/2025 (AGOL2026.R1) | Revit models that rely solely on address information for geolocation have misaligned 2D and 3D output | When Revit models rely solely on address information for geolocation, the 2D bounding box and 3D Models layer output are misaligned. Workaround: Use one of the recommended georeferencing methods outlined in Georeferencing workflows. | ||
01/09/2026 (AGOL2026.R1) | Non-cloud Revit models fail to ingest to GeoBIM if they are not detached from central file | Non-cloud Revit files uploaded to the Autodesk cloud without being detached from the central file will fail to ingest in GeoBIM. When this happens, the error log lists the failures with the message Exception: No 3D model available. Workaround:
See Autodesk support to learn more. | Bug identified | |
12/05/2025 (AGOL2026.R1)
| IFC models fail to ingest to GeoBIM when only lat/long coordinates are stored in IFCSITE entity | IFC models that only contain lat/long coordinates, stored in the IFCSITE entity, will fail during the GeoBIM tool run as the models do not include an IfcMapConversion or IfcProjectedCRS entity to define spatial reference. When this happens, the error log lists the failure with the message Exception: No spatial reference available. Workaround: Embed the geolocation information directly within the IFC model by including the coordinates and specifying the coordinate system in the appropriate IFC entities. | Bug identified | |
10/24/2025 (AGOL2025.R3) | IFC4 3D Models layer output positioned at the wrong elevation/horizontal location | Some IFC4 models are positioned at the wrong Z-axis or XY-axis when the elevation/XY coordinates are defined in the IfcMapConversion entity. Workaround:
| Bug identified | |
09/02/2025 (AGOL2025.R3) | Export tool no longer available by default in new ArcGIS GeoBIM projects | The Export tool in the table widget is no longer available by default for new GeoBIM projects. Workaround:
| Bug identified | N/A |
08/22/2025 (AGOL2025.R3) | Issue dot is sometimes not appearing when creating a new project issue in a web scene. | The issue dot sometimes may not appear in the scene view when creating a new issue in the GeoBIM app. The issue point can still be placed in the scene and the new issue can be created and uploaded to the source BIM project. | Bug identified | N/A |
09/18/2025 (AGOL2025.R3) | Building scene layers cannot be selected in Link Rules table menu | Building scene layers cannot be selected in the menu of the Link Rules table. Workaround:
| Bug identified | N/A |
07/21/2025 (AGOL2025.R3) | Autodesk Viewer widget crashes if app remains open past the initial token expiry time | The Autodesk Viewer widget may display an error message if a model is rendered in the viewer and the app remains open past the initial token expiry time. Workaround:
| Bug identified | N/A |
06/24/2025 (AGOL2025.R2) | Runtime error in project web scene | A runtime error appears when you open the project web scene in Scene Viewer due to an incomplete configuration. Workaround:
| Bug identified | N/A |
07/08/2025 (AGOL2025.R2)
| Corrupted ACC/BIM360 files cause constant loading state in the APS Viewer within ArcGIS GeoBIM, if previewed. | Files in ACC/BIM360 that have processing errors cause a constant loading state in the APS Viewer inside GeoBIM when you attempt to preview them. | Bug identified | N/A |
07/03/2025 (AGOL2025.R2) | When GeoBIM project is connected to 'All projects', the Select Folders modal shows incorrect folder selection after signing out of and back into ArcGIS and Autodesk accounts. | When a GeoBIM project is connected to 'All projects', the folder tree in the Select Folders modal does not display the last jobs custom selection if you sign out and back into your ArcGIS and Autodesk accounts. Workarounds:
| Bug identified | N/A |
07/02/2025 (AGOL2025.R2) | Linked Document field in Create New Issue doesn't show 'No document' message if new issue is placed on document with no Autodesk access (only if issue was previously placed on document user has access to) | If you update new issue placement to a document you do not have access to the Linked Document field will show the documents from the prior placement. It should instead display 'No document found at this location'. Workaround: Close the Create New Issue widget and place the issue on the document you don't have access to. The 'No document found at this location' message displays. | Bug identified | N/A |
06/25/2025 (AGOL2025.R2) | Elevation limitations in a project web scene in local coordinates | If the ArcGIS GeoBIM project's coordinate system is other than web mercator (EPSG 3857) or WGS84 (EPSG 4326), the resulting project web scene will have no elevation services added. As a result, the models might be flying up in the air, since The elevation layer (Terrain3D) provided by Esri, only supports web mercator and WGS84. Workaround: You will need a custom web elevation layer published for the project area. In order to publish your own elevation layers, please visit ArcGIS Pro help pages. | Bug identified | N/A |
06/25/2025 (AGOL2025.R2) | Only Save to Copy possible when the project web scene is added to a GeoBIM app | If the project web scene is added to an ArcGIS GeoBIM app, only the "Save as" option is available. A project web scene is generated only if you run the new “Add Document Models” tool in the Tools page in ArcGIS GeoBIM. Workaround:
| Bug identified | N/A |
06/25/2025 (AGOL2025.R2) | Runtime error in web scene viewer with an incomplete configuration in the project web scene. | When the project’s web scene is opened in the web scene viewer, a runtime error (Webscene not valid against schema) shows up because of an incomplete configuration. This web scene is generated only if you run the new “Add Document Models” tool in the Tools page in ArcGIS GeoBIM. Workaround: Ignore and close the error message. Save the web scene as it is. The error message won’t show up. | Bug identified | N/A |
06/11/2025 (AGOL2025.R2 ) | Projects list does not show in Accounts modal after logging back in to GeoBIM | The projects list in the Accounts modal is blank if you log in to GeoBIM directly on the Accounts page. Previously, the Autodesk login would automatically display upon logging in. Workaround: Click another tab in the UI to force the Autodesk login. Return to the Accounts page and the projects list will be displayed. | Bug identified | N/A |
04/25/2025 (AGOL2025.R2) | “NN” Norwegian browser locale displays in English | ArcGIS GeoBIM UI will display in English if the browser locale is set to “NN” Norwegian. | Bug identified | N/A |
02/15/2025 (AGOL2025.R1) | ACC Model Sets not displaying in GeoBIM | ACC Model Sets currently will not display in the Document Explorer widget. | Bug identified | N/A |
12/05/2024 (AGOL2025.R1) | Add Links button is removed from the Link Explorer when editing widget positioning | The Add Links button is removed from the Link Explorer widget if you edit the arrangement of the widgets without having a feature selected. Workaround: Select a feature before editing the arrangement of the widgets. | Bug identified | N/A |
11/01/2024 (AGOL2024.R3 & Enterprise 11.4) | ACC Issues created in sheet view is not always opened correctly from ArcGIS GeoBIM Issue Details | If an ACC issue was created in a sheet view, then clicking the link next to ‘Open in source’, in the GeoBIM Issue details, will not open the issue dot in the sheet in the source project. Workaround: Select the correct view in the ACC source project to view the related issue. | Bug identified | N/A |
10/30/2024 (AGOL2024.R3 & Enterprise 11.4) | Bookmarks are saved only in the browser's local storage. | Bookmarks created in the GeoBIM app will only be saved to the local storage. If you open a new incognito window, new browser, or clear your cache the bookmark you created will be lost. See Use the Bookmark widget to learn more. Workaround: Create your bookmarks in Map Viewer or Scene Viewer so they can be permanently saved. | Experience Builder bug. We will not fix this. | N/A |
10/29/2024 (AGOL2024.R3 & Enterprise 11.4) | Feature link name does not update if renamed in the source ACC project | The feature link names in the Link Explorer will not update if renamed in the source project. Workaround: Recreate the link in GeoBIM to have the new name displayed. | Bug identified |
|
08/15/2024 (AGOL2024.R2) | Revit 3D issues are not using Revit rotation | Issues from ACC and BIM 360 are not rotated to align with the orientation of the document. | Bug identified | N/A |
09/29/2023 (AGOL2023.R2) | BIM 360 Issues created in GeoBIM will be placed at center of the linked document after rerunning tools. | BIM 360 issues that are created in GeoBIM will lose their original location after rerunning the tools. This is because BIM 360 does not use lat/long locations for project issues. | Bug identified | N/A |
09/20/2023 (AGOL2023.R2) | I18N-RTL: Arrow icons are not flipped on Tools page History tab | When working in right-to-left script the arrow icons for the Tools page History tab are not flipped. The icons should point in the opposite direction. | Bug identified | N/A |
Date Identified (Software Release) | Title | Description | Status | Bug ID (if applicable) |
05/23/2025 (AGOL2025.R2) | Race condition issue on switch when loading from the previous job | After refreshing and immediately opening the settings on the Add Document Extents card, the Add thumbnails as attachments switch will be disabled. | Fixed
Settings button is now disabled for the Add Document Extents tool card until page load finishes. | N/A |
02/14/2025 (AGOL2025.R1) | BIM360 Model Sets cannot be linked to features | BIM360 Model Sets could not be linked to features in GeoBIM | Fixed
Model Sets from BIM360 (that are set up for Clash Testing) can now be linked to features in GeoBIM. | N/A |
02/05/2025 (AGOL2025.R1)
| Field Maps Designer Form returning errors if processing is interrupted | If you interrupt the processing after enabling a map for the field errors were returned in the form configuration. | Fixed
Pop up message displays after enabling a map for the field stating, ‘Field Maps Designer will open in a new window after processing has finished.’ This popup cannot be closed. |
|
10/16/2024 (AGOL2024.R2) | Files with empty geometry are ingested into GeoBIM | Files with empty geometry are being ingested into the GeoBIM project during the tools run. | Fixed
Files with empty geometry are now skipped during the tools run. | N/A |
09/19/2024 (AGOL2024.R3 & Enterprise 11.4) | Field Maps forms not configured correctly if map contains grouped layers | When maps contain grouped layers there is an issue with enabling Field Maps. The forms are not being configured correctly. | Fixed
Field Maps form will now be configured correctly if map contains grouped layers. The New Field Maps Issues layer will be placed outside of the group layers. | N/A |
11/11/2021 (AGOL2024.R3) | Tools does not correctly georeference Revit or IFC files with user specified WKID | Given a Revit or IFC file where the coordinates are correctly specified based on a coordinate system WKID, entering the WKID in the tools page does not result in creating the document boundary in the spatial reference. Depending on the coordinates of the file this will result in the boundary in the wrong location or with no geometry | Fixed
| BUG-000144459
|