Fixed
Status Update
Updated by @
We are actively working on this issue and will resolve it before decommissioning the Legacy renderer.
Comments
ee...@google.com <ee...@google.com> #2
the error happens when calling UrlFetchApp.fetch()
ee...@google.com <ee...@google.com>
ja...@google.com <ja...@google.com> #3
Comment has been deleted.
ja...@google.com <ja...@google.com> #4
Comment has been deleted.
ja...@google.com <ja...@google.com> #5
Comment has been deleted.
ja...@google.com <ja...@google.com> #6
Comment has been deleted.
as...@google.com <as...@google.com> #7
We're also experiencing this issue when calling UrlFetchApp.fetch()
Our production system is down.
as...@google.com <as...@google.com> #8
[20-12-09 10:26:13:787 EST] Exception: Unexpected error: URL[Redcated for privacy purposes]
at get_csv1d_(Code:31:30)
at auxIMP(Code:63:17)
No idea what the error codes mean but this is also affecting exports of CSV files from a URL and attempting to import and parse them. It can't fetch the URL. I can manually access the same link and it works fine so I know this is on Google's end.
at get_csv1d_(Code:31:30)
at auxIMP(Code:63:17)
No idea what the error codes mean but this is also affecting exports of CSV files from a URL and attempting to import and parse them. It can't fetch the URL. I can manually access the same link and it works fine so I know this is on Google's end.
as...@google.com <as...@google.com> #9
We are also experiencing this issue in Google AppScript. For us it seems to happen specifically when fetching CSV files, and it happens 100% of the time. Just started occurring this morning or late yesterday.
We confirmed that the same files are being fetched without an issue outside of AppScript.
We confirmed that the same files are being fetched without an issue outside of AppScript.
as...@google.com <as...@google.com> #10
same
Description
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Please put together a simplified reproduction case, and put it up as a project on your choice of git hosting providers (e.g. github, bitbucket, etc). The easiest way to do this might be to fork the Google Maps Android API Samples Repository and modify one of the existing demo activities:
What steps will reproduce the problem?
1. Map.setBuildingsEnabled(true), 3D building is Turn on 。
2. draw Lines or Circle with addPolyline() or addCircle()
3. zoom the map to Level 18,you can see the lines is blocked
Also add the following details:
- Device (and version of Android) you have verified this issue on: Any phone, For example, samsung/SM-G532M.
- Google Play Services client library version:
- Google Play Services version on the device: 22.26.15(100408-461192076)
- Android SDK Version: com.google.android.gms:play-services-maps:18.0.0
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?)
Also attach screenshots, sample code and optionally an APK if possible.
This problem can occur with MapsInitializer.Renderer.LATEST , but not MapsInitializer.Renderer.LEGACY。
My code:
final int initialize = MapsInitializer.initialize(context.getApplicationContext(), MapsInitializer.Renderer.LATEST, new OnMapsSdkInitializedCallback() {
@Override
public void onMapsSdkInitialized(@NonNull MapsInitializer.Renderer renderer) {
Log.e("TAG", "google onMapsSdkInitialized :" + renderer);
}
});
If the problem exhibits itself in a released version of your app on the
Play Store, optionally provide a link to the app, and explain how to
reproduce the issue in the app.