Fixed the issue where the file size could not be correctly obtained within the HarmonyOS Next sandbox. #19100
+8
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re: #
Changelog
Continuous Integration
This pull request:
Compatibility Check
This pull request:
Greptile Overview
Greptile Summary
This PR fixes a file size retrieval bug specific to HarmonyOS Next sandbox environment. The issue was that the
getFileSize()method in the HarmonyOS platform adapter was incorrectly attempting to handle absolute file paths (starting with '/') using the HarmonyOS ResourceManager API, which is intended only for bundled assets. The fix adds a simple check to delegate absolute paths to the baseFileUtils::getFileSize()method, ensuring they are handled by standard filesystem operations instead.This change aligns with the existing pattern already implemented in other methods like
getContents()andisFileExistInternal(), creating consistency across the HarmonyOS file handling implementation. The change is platform-specific and contained within the HarmonyOS adapter, maintaining the engine's cross-platform file access abstraction while properly supporting both asset bundle files and absolute filesystem paths on HarmonyOS.Important Files Changed
Confidence score: 5/5