Known Issues & Fixes¶
If you run into something unexpected, check the list below. If your issue isn't covered, feel free to open a GitHub issue or reach out directly at ansukhetskyi@cloudrylabs.com.
"View All" Attachments page opens and immediately closes
When does it happen?
In some sandbox environments, clicking "View All" on the Google Client: Attachments component causes the page to open briefly and close itself automatically.
Root Cause
This happens when Platform Cache is unavailable. During installation, the package creates a Platform Cache Partition named GoogleCloudClient. If your sandbox has 0 cache storage provisioned, screens that rely on Platform Cache may fail to load.
Fix
- Go to Setup
- Search for Platform Cache
- Click into the partition named GoogleCloudClient
- Click Edit
- Under Provider Free, set: Session Cache =
1and Org Cache =1 - Save
This allocates minimal cache and resolves the issue.
"Google Client Config" record shows a deprecation warning after upgrading to v1.3.0
When does it happen?
After upgrading to v1.3.0, opening the GoogleClientConfig__mdt record in Setup (Custom Metadata Types → Google Client Config → Manage Records) may display the following banner:
This Google Client Config has been marked deprecated. You might lose any changes you make to the component if you later upgrade to a package version that restores it.
Why does this happen?
In previous versions, the package shipped a pre-built GoogleClient metadata record. On every upgrade, Salesforce re-deployed it as a full overwrite — silently wiping any values you had manually configured (certificate name, service account email, API keys, etc.).
To prevent this data loss, the record was removed from the package in v1.3.0. Salesforce marks it as deprecated because it no longer belongs to any package version — which is exactly the intent.
Is anything broken?
No. Your configuration data is intact, the app continues to work exactly as before, and no action is required. The warning is purely informational.
"Data Not Available" error during authentication or setup
When does it happen?
You may see this message in Salesforce:
Data Not Available: The data you were trying to access could not be found.
In this context, it usually means the Salesforce Identity Provider is not enabled for the org.
Fix
- Go to Setup.
- Search for Identity Provider in Quick Find.
- Open Identity Provider.
- Click Enable Identity Provider.
- Click Save.
- Return to Google Client setup and try the action again.
"Certificate cannot be null" when saving and validating Google Drive configuration
When does it happen?
This can happen the first time you save and validate Google Drive configuration in the Google Client app.
Root Cause
The configuration save and validation can run too close together. The save is still being committed when validation starts, so validation may not see the certificate information yet and returns a certificate error.
Fix
- Save the Google Drive configuration.
- Wait 10-15 seconds.
- Click Validate again.
- If the same message appears, wait a little longer and click Validate again.
After the authentication details finish saving, validation should use the new certificate information correctly.