Skip to content

Fix: release mode on IOS files fetching not working#567

Merged
mlodyjesienin merged 2 commits intomainfrom
@mlodyjesienin/release-mode-resource-fetcher
Aug 28, 2025
Merged

Fix: release mode on IOS files fetching not working#567
mlodyjesienin merged 2 commits intomainfrom
@mlodyjesienin/release-mode-resource-fetcher

Conversation

@mlodyjesienin
Copy link
Copy Markdown
Contributor

Description

There was a bug in the ResourceFetcher in the logic of handling release builds bundled files fetching.
Not only the condition, on which we previously decided whether it is DEV MODE or RELEASE MODE was wrong but also the moveAsync in handling logic caused app crashes on IOS.
On the android previous version was working, but approach utilizing copyAsync seems better suited and clearer version.

Introduces a breaking change?

  • Yes
  • No

Type of change

  • Bug fix (change which fixes an issue)
  • New feature (change which adds functionality)
  • Documentation update (improves or adds clarity to existing documentation)
  • Other (chores, tests, code style improvements etc.)

Tested on

  • iOS
  • Android

Testing instructions

Screenshots

Related issues

Checklist

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Additional notes

@mlodyjesienin mlodyjesienin merged commit 6aeb834 into main Aug 28, 2025
2 checks passed
@mlodyjesienin mlodyjesienin deleted the @mlodyjesienin/release-mode-resource-fetcher branch August 28, 2025 12:56
mlodyjesienin added a commit that referenced this pull request Aug 28, 2025
## Description

There was a bug in the `ResourceFetcher` in the logic of handling
release builds bundled files fetching.
Not only the condition, on which we previously decided whether it is
`DEV MODE` or `RELEASE MODE` was wrong but also the `moveAsync` in
handling logic caused app crashes on IOS.
On the android previous version was working, but approach utilizing
`copyAsync` seems better suited and clearer version.

### Introduces a breaking change?

- [ ] Yes
- [x] No

### Type of change

- [x] Bug fix (change which fixes an issue)
- [ ] New feature (change which adds functionality)
- [ ] Documentation update (improves or adds clarity to existing
documentation)
- [ ] Other (chores, tests, code style improvements etc.)

### Tested on

- [x] iOS
- [x] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [x] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
KnextKoder pushed a commit to Synkhiv/react-native-executorch that referenced this pull request Nov 7, 2025
…#567)

## Description

There was a bug in the `ResourceFetcher` in the logic of handling
release builds bundled files fetching.
Not only the condition, on which we previously decided whether it is
`DEV MODE` or `RELEASE MODE` was wrong but also the `moveAsync` in
handling logic caused app crashes on IOS.
On the android previous version was working, but approach utilizing
`copyAsync` seems better suited and clearer version.

### Introduces a breaking change?

- [ ] Yes
- [x] No

### Type of change

- [x] Bug fix (change which fixes an issue)
- [ ] New feature (change which adds functionality)
- [ ] Documentation update (improves or adds clarity to existing
documentation)
- [ ] Other (chores, tests, code style improvements etc.)

### Tested on

- [x] iOS
- [x] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [x] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants