Experience Cloud Guest User

[taits]

Wondering if logging from Apex executed with an Experience Cloud guest user should work? Any specific permissions need to be added to the Sites Guest user Profile?

Seeing a Salesforce System Error on line 2656 of Logger.apxc
String transactionId = System.Request.getCurrent().getRequestId();

[jongpie]

Hey @taits! Yeah, my goal is that logging should work for Experience Cloud (including the guest user), but it sounds like there might be a bug for the guest user scenario. Any chance you could share a stack trace string for the error that happens on that line? My guess is that for the guest user, Salesforce probably doesn't provide a request ID, so I'm guessing System.Request.getCurrent() is null --> it fails on the chained call to getRequestId(). If that's the case, then I think it should be a (hopefully) easy fix to make.

[mohitlakde]

Thank you @jongpie Sorry not to mentioned earlier, apart from Community normal login, user can login through Social platform as well. I have not tested with regular Community logged-in user, but can you test for Social(Facebook or Google) Logged-in user.

Scenario:
Every time when User logs in through social platform we are capturing incoming details in Salesforce.

Logger.info(String.valueOf(data)); //data is incoming Auth.UserData
Logger.saveLog();

[mohitlakde]

@jongpie i tried for regular community user as you mentioned and it worked, but still fails for community user when they login using social accounts, specifically if we put this logger saving line in social controller.

[jongpie]

@mohitlakde thanks for the details! I was finally able to reproduce this issue in a scratch org - I've logged it as a bug, issue #224. I was able to create a quick prototype to bypass the issue, and I was then able to successfully save logs from an auth provider registration class (see screenshot below), so there should definitely be a way to get this working soon. I'm going to keep exploring options for how to best implement a workaround for the problem - I'll try to have a fix done ASAP!

[jongpie]

@mohitlakde I think I've found a workaround for this issue - could you try out this beta package version in one of your sandboxes/scratch orgs to see if it solves the issue for you? It solved it for me in a scratch org I setup, but just want to be sure it's working for you too, before I merge the changes.

• New beta package version - https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5Y0000015l1OQAQ
• Relevant changes - d1ca055

I'm hoping to include this in PR #218 (v4.6.10) - let me know if you run into any issues.

[jongpie]

@mohitlakde and @taits I did some more testing and everything seems to be working now, so I've included a bugfix for this in the new release v4.6.10. Hopefully everything is now resolved, but let me know if you run into any more issues!