Status Update
Comments
[Deleted User] <[Deleted User]> #2
A Null Pointer Exception in Nav Controller when switching the start destination typically happens due to one of the following reasons:
Incorrect Initialization: The NavController might not be properly initialized before trying to set a new start destination. Ensure that the NavController is correctly associated with the Nav Host Fragment or Fragment Container View. Navigation Graph Not Set: If the navigation graph is not set before switching the start destination, it can lead to a Null Pointer Exception. Make sure the navigation
[Deleted User] <[Deleted User]> #3
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Fix NavDestination mismatch when adding NavBackStackEntry
Expand for full commit details
Fix NavDestination mismatch when adding NavBackStackEntry
When navigating to a nested NavDestination, we trace the target destination's hierarchy and add its parents to the backstack. Since a destination can have different parents (i.e. same destination exists within different graphs), we check its parent for referential equality and add it only if that specific parent hasn't been added yet.
Part of this process includes searching for a specific parent instance. However, parents can also be duplicated - a parent destination can also exist in several different graphs. The current bug is due to findDestination returning the wrong parent duplicate.
So findDestination is modified to take an optional matchingDestination parameter. When matchingDestination is present, findDestination will attempt to return a destination that is equal (==) and has the same parent (same nesting) as the matchingDestination.
Bug: 361560785
Test: ./gradlew navigation:navigation-runtime:cC
Relnote: "Fixed NavDestination NullPointerException when updating a Graph's startDestination"
Change-Id: I99421bf1e4aef9802873d9d78fbc6fafc15a21ba
Files:
- M
navigation/navigation-common/src/main/java/androidx/navigation/NavGraph.kt
- M
navigation/navigation-runtime/src/androidTest/java/androidx/navigation/NavControllerRouteTest.kt
- M
navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.kt
Hash: 7341ef64fbf832915b8ee6c1ed4838b5981fd886
Date: Wed Nov 13 11:45:32 2024
ry...@google.com <ry...@google.com>
jb...@gmail.com <jb...@gmail.com> #4
Fixed internally and available in navigation 2.8.5
.
[Deleted User] <[Deleted User]> #5
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.navigation:navigation-common:2.9.0-alpha04
androidx.navigation:navigation-runtime:2.9.0-alpha04
androidx.navigation:navigation-common:2.8.5
androidx.navigation:navigation-runtime:2.8.5
[Deleted User] <[Deleted User]> #6
ry...@google.com <ry...@google.com>
ek...@google.com <ek...@google.com> #7
As a workaround, you can use the Drive v2 API's files.get() endpoint to retrieve the exportLinks for the file and fetch that URL instead. From my testing that URL does not have the same limit as files.export() and more closely matches the behavior seen in the Google Docs UI's "File > Download as" menu item.
I'll keep this issue open for now as I discuss other options with the engineering team.
ek...@google.com <ek...@google.com> #8
Files.export() remains an option, but the exportLinks is a bit more durable as it shouldn't run into the exportSizeLimitExceeded error for large files.
ra...@gmail.com <ra...@gmail.com> #9
I am using 'google-api-services-drive' in version v3-rev20181213-1.28.0, and I am always getting null from getExportLinks(), even in the case of Google files and even from other types.
any help?
ek...@google.com <ek...@google.com> #10
ra...@gmail.com <ra...@gmail.com> #11
ro...@gmail.com <ro...@gmail.com> #12
Is there un update or workaround on this ?
We have customers migrating data between Shared Drive, and this is cauasing too many issues.
Why are we posing this hard limitation on native files ?
sg...@team-gforce1.com <sg...@team-gforce1.com> #13
Hello Team,
System is throwing "This file is too large to be exported" error when we are exporting Google Forms in zip file. For small Google forms it's working fine.
For Large google forms Google Drive API V3 is throwing error. Please find below error for your reference.
Download failed for 'untitled form' with id:1_WzWtx3djdJlDn5mh3tsyO9QXYBv1dN1TR6sRviwFR8. Reason: This file is too large to be exported.
Thanks
ad...@contractors.roche.com <ad...@contractors.roche.com> #14
sk...@gmail.com <sk...@gmail.com> #15
I'm using NodeJS
st...@snowflake.com <st...@snowflake.com> #16
This has kept being an issue, why a limitation has been set? Can we ask our company Google admin to remove the limit?
st...@snowflake.com <st...@snowflake.com> #17
export link does not work in the same equivalent of files().export_media(), there is a specific need on diffenent use cases. convert gslides/gdoc to pdf will break the essential underlying content structure. and cannot be used as a replacement. Pls provide the equivalent solution. thanks
Description
not already been reported.
Please provide a short description of the issue:
I use rest api "
to get google Doc.
I have document when the exported document file size ~ 5 MB i had the json error :
{
"error": {
"errors": [
{
"domain": "global",
"reason": "exportSizeLimitExceeded",
"message": "This file is too large to be exported."
}
],
"code": 403,
"message": "This file is too large to be exported."
}
}
When the exported document file size < 5 MB the file exported successfully, My problem in exported document file size > 5 MB
Please provide a small code sample that reliably reproduces the issue.
The sample should run as-is or with minimal setup, without external
dependencies.
Used rest api "
As POST request with "Authorization" Header.
What steps will reproduce the problem?
2.observe the result.
What is the expected output? What do you see instead?
return exported file without limits.