Skip to content

Map page is blank, was working earlier #41

Open
Open
Map page is blank, was working earlier#41

Description

@rgry
rgry
opened on Feb 25, 2023

First, Thank you for a great hack! Even though I think Adobe should have fixed it in the first place....

I had you fix running on my mac for over a year now, but not it does not work any more?
Just for testing I installed LR6 on my windows and gone through the steps and it does not work here either?
Map page is kind of blank? Not showing any errors?

I'm I the only one? or did Adobe/Google change something? Where do I look for a log?

Activity

  1. Peter-MI commented on Feb 25, 2023

    @Peter-MI
    Peter-MI
    on Feb 25, 2023

    Same here on Windows 11. Google first showed error in the account console and Lightroom showed “request denied” but now it just doesn’t work anymore

  2. astuder commented on Feb 25, 2023

    @astuder
    astuder
    on Feb 25, 2023
    Owner

    Uh, oh! SaaS bit rot may finally catch up with us. 😢

    I also get the blank screen. But didn't get a "request denied" message and don't see errors in the Google cloud account console. The only thing I see in the cloud console, is that there are calls to the Geocoding API but no calls to the Maps Javascript API. I see both calls on Feb19 when I last used Lightroom maps.

    If anyone has more details about error messages, or maybe even a HTTP logs, please share. But don't forget to redact API keys.

  3. astuder commented on Feb 25, 2023

    @astuder
    astuder
    on Feb 25, 2023
    Owner

    I wonder if this is related to deprecation of Google Maps JavaScript API V2
    https://developers.google.com/maps/documentation/javascript/v2tov3

  4. Peter-MI commented on Feb 25, 2023

    @Peter-MI
    Peter-MI
    on Feb 25, 2023

    But they say V2 was made unavailable in May 2021… also the OSM hack does not work anymore: bottom left menu does only show LR original map styles

  5. astuder commented on Feb 27, 2023

    @astuder
    astuder
    on Feb 27, 2023
    Owner

    I looked at this today, and can't figure out where it fails. It seems that it fails creating the map view even before calling Google.

    Can everyone that encounters the issue please state their platform? I'm on Windows 11 like Peter. Any Mac users?

  6. senarvi commented on Feb 27, 2023

    @senarvi
    senarvi
    on Feb 27, 2023

    Same thing with me on Windows 11.

  7. teskeyn commented on Feb 27, 2023

    @teskeyn
    teskeyn
    on Feb 27, 2023

    I'm still on WIndows 10 and have the same symptoms with LR6. I noticed in my Google cloud console that there was a recommendation that I restrict my key to adobe.com, which I don't recall seeing before. Is LR6 actually sending the request to Google via adobe.com, and Adobe have now blocked it; but that doesn't make any sense to me and wouldn't explain why the OSM hack fails

  8. softnorbi commented on Feb 27, 2023

    @softnorbi
    softnorbi
    on Feb 27, 2023

    Exactly the same on my PC with Windows 10 😢 Only the reverse geocoding ("LR adresss suggestions") still works for the GPS data in the picture. Map search however e.g. for the state name doesn't work as well. I just looked on the google maps platform and my last recognized requests to MapsJavaScript API have been on Thursday 23. Feb. , without any errors recordet at that time and since then...

  9. astuder commented on Feb 27, 2023

    @astuder
    astuder
    on Feb 27, 2023
    Owner

    Any Mac users? Never mind, just noticed that the original poster is running on Mac. So definitely not a platform issue.

    @teskeyn do you have more details about the recommendation regarding key restriction? A newly enforced security measure (like CORS) sounds like a "good" candidate.

  10. teskeyn commented on Feb 28, 2023

    @teskeyn
    teskeyn
    on Feb 28, 2023 via email

  11. Peter-MI commented on Mar 1, 2023

    @Peter-MI
    Peter-MI
    on Mar 1, 2023

    @teskeyn: interestingly the old Geosetter now also does not work anymore - map requests end with "01.03.2023 15:51:12 ERROR: Could not complete the operation due to error 80020101
    showMap3(2, 4, 45.4741962777, 9.1738253847, 10);"

  12. teskeyn commented on Mar 1, 2023

    @teskeyn
    teskeyn
    on Mar 1, 2023 via email

  13. astuder commented on Mar 2, 2023

    @astuder
    astuder
    on Mar 2, 2023
    Owner

    Oh, that's interesting about Geosetter. The two relevant tickets seem to be:
    https://geosetter.de/mantis/view.php?id=2261
    https://geosetter.de/mantis/view.php?id=2256
    A quick search in location.lrmodule didn't bring up showMap3, but maybe there are similarities with our issue.

    Unfortunately, I won't have time the next few days to dig deeper into this.

  14. diabWH3 commented on Mar 11, 2023

    @diabWH3
    diabWH3
    on Mar 11, 2023

    Just chiming in to say that I'm also experiencing this issue with Windows 10 and Lightroom Classic 6.13.
    This fix has allowed me to keep using this paid-for software for far longer than Adobe would have otherwise allowed, so I appreciate all the hard work of this community!

  15. diabWH3 commented on Mar 11, 2023

    @diabWH3
    diabWH3
    on Mar 11, 2023

    This may be related, but I no longer seem to be able to manually adjust the Country/State/City/Sublocation metadata fields for my photos. In the Grid/Loupe views, I can manually type something into those metadata fields, but upon hitting Enter, the application does not save my entries.

    DISREGARD: I restarted Lightroom and the Metadata panel works as intended. Just a weird glitch.

  16. 80 remaining items

  17. senarvi commented on Feb 27, 2024

    @senarvi
    senarvi
    on Feb 27, 2024

    Scratch that. The whole thing is heavily tied to the Google Maps JavaScript API. The Google API is used for interacting with the map and OpenStreetMaps is used just for rendering the map tiles. I don't think there's other way except to get the Google API working.

  18. senarvi commented on Feb 27, 2024

    @senarvi
    senarvi
    on Feb 27, 2024

    I tried something desperate, hoping to catch some kind of error - I tried to enclose every function in a try..catch block. Basically replacing every Lua block like this (find_top_level_braces() finds the first { and last } of a function):

        new_code = ""
    previous_end = 0
    pattern = re.compile("function([^)]*)")
    for match in pattern.finditer(code):
        start_index = match.end()
        indices = find_top_level_braces(code, start_index)
        if indices is not None:
            first, last = indices
            new_code += code[previous_end:first + 1]
            new_code += " try {"
            new_code += code[first + 1:last]
            new_code += "} catch (e) { alert( e.message ); } "
            previous_end = last
    new_code += code[previous_end:]

    Still nothing happened in Lightroom.

  19. astuder commented on Feb 27, 2024

    @astuder
    astuder
    on Feb 27, 2024
    Owner

    I apologize for my inactivity on this project. Other projects keep me very busy these days. :-/

    I suspect that the failure doesn't happen when rendering the HTML page, but in JavaScript code directly invoked from Lua, and/or the interface between the two. For example a change in a Google Maps data structure causing an error in the LUA code processing it.

  20. Cassiopeiaaa commented on Mar 19, 2024

    @Cassiopeiaaa
    Cassiopeiaaa
    on Mar 19, 2024

    I just wanted to add that in my google-account I can see that LR6 is communicating with google and that the "error rate"(?) is 0%.
    Just to let you know. Maybe the answer is misinterpreted from LR6. (but I have absolutely no programming-skills).

  21. vb0 commented on Jan 29, 2025

    @vb0
    vb0
    on Jan 29, 2025

    WARNING: starting March 1st 2025 there are billing changes for the Maps API. No more $200 monthly free credit but there are a number of free "billable events" (go figure...).

    From what I see we would be using Maps JavaScript API (which is broken so no events) and Geocoding API when ingesting the pictures (this is still of some use at it'll reverse geocode the country/state-province/city). This Geocoding API belongs to "Essentials" SKU after March 1st and will get supposedly 10k free hits but I'm not sure if this segregation into Essentials/Pro/Enterprise means some monthly billing too ... and if it doesn't now I'm sure it could well come in some time.

    Anyone can comment? I would keep this if free, although of little value still isn't zero, at the same time I don't feel good about leaving this sprawling, ever changing and risky Google Cloud/Maps API enabled at all.

  22. diabWH3 commented on Jan 29, 2025

    @diabWH3
    diabWH3
    on Jan 29, 2025 via email

  23. astuder commented on Oct 26, 2026

    @astuder
    astuder
    on Oct 26, 2026
    Owner

    Anyone still using Lightroom classic? We might have something cookin' :)

  24. jbd7 commented on Oct 26, 2026

    @jbd7
    jbd7
    on Oct 26, 2026

    31. Anyone still using Lightroom classic? We might have something cookin' :)

    Yes, working fine on LR12. Curious ...

  25. vb0 commented on Oct 26, 2026

    @vb0
    vb0
    on Oct 26, 2026

    30. Anyone still using Lightroom classic? We might have something cookin' :)

    Sure, the only thing is I (hopefully) nuked all my Google everything related to API usage, I have loss aversion off the charts and I didn't want to be charged for something I can't even use next time they reshuffle their pricing structure. If it's somehow doing openstreetmaps or anything we can self-host it would be better. It didn't cross my mind before but if these LLMs can clone most of Adobe's stuff, probably they can help to vibe code some API endpoint too ...

  26. reinhardstenger58-creator commented on Oct 26, 2026

    @reinhardstenger58-creator
    reinhardstenger58-creator
    on Oct 26, 2026

    Hi, Ichnutze immer noch LR 6.14 und wäre sehr dankbar wenn das Kartenmodul wieder funktionieren würde

  27. softnorbi commented on Oct 26, 2026

    @softnorbi
    softnorbi
    on Oct 26, 2026

    Hi,
    it would be realy great if the LR 6.x Google issue could be solved! I'm working with current LRC but miss LR 6.x that was working without Adobe cloud useage....

  28. diabWH3 commented on Oct 26, 2026

    @diabWH3
    diabWH3
    on Oct 26, 2026 via email

  29. astuder commented on Oct 26, 2026

    @astuder
    astuder
    on Oct 26, 2026
    Owner

    Advanced users only: I added a few more bits to the repository (see /patches folder). Below are the draft instructions. I only tested this on Windows 11 with a location.lrmodule that was already patched with the old fixes, so there may be bugs with a virgin module or on Mac. Please report success and failures.
    https://github.com/astuder/lightroom-map-fix/blob/master/README-mapfix-shim.md

    Most of the credit goes to Claude. I gave it a link to this repository, and a folder with LUA files that I decompiled with unluac. It probably could have done the last step itself. After a few minutes of analyzing the LUA code it proposed to implement the shim. My only role was to test with a real Lightroom and give some directions on the features. Truly impressive. Good thing I no longer do computers for a living :)

    This approach should work to hack on other Lightroom modules, probably even Lightroom itself, including the subscription-only versions.

  30. diabWH3 commented on Oct 26, 2026

    @diabWH3
    diabWH3
    on Oct 26, 2026

    @astuder can you add this to the actual repo? This is awesome work and I'm excited to try it out when I get some time.

     [README-mapfix-shim.md](https://github.com/user-attachments/files/33977741/README-mapfix-shim.md)

  31. astuder commented on Oct 26, 2026

    @astuder
    astuder
    on Oct 26, 2026
    Owner

    Here you go: https://github.com/astuder/lightroom-map-fix/blob/master/README-mapfix-shim.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions