Retry mechanism for bundle downloads

[ofalvai]

I'm happy to contribute this feature, but want to get some alignment first from the maintainers and whether this is a good idea.

I looked at how the native downloader implementations handle retry, and I don't see anything that would retry transient server errors like HTTP 500 (that would be my #1 concern, but retrying other errors would be also useful)

• iOS implementation uses NSURLConnection, which AFAIK doesn't retry on high-level errors like HTTP status codes
• Android implementation uses java.net.HttpUrlConnection. I couldn't find anything conclusive about its retry logic.
• Windows: TODO, haven't checked yet

I would expect this auto-retry to be configurable with the usual parameters like max attempts, initial delay, exponential backoff params, etc.

Is it something that would make sense for the project?

[CHOIMINSEOK]

Hi! @ofalvai

I’m really glad to see your suggestion. I definitely agree — it would be very useful if we could make the retry options configurable at the React Native application level. Currently force update failure rate is quite high in production environment, and this feature might mitigate this issue.

Let me know if you need any help on this feature ! cc @kmsbernard

[ofalvai]

Sounds good! I think I'll have some time this week to hack on this and share an early draft.

[ofalvai]

Submitted my inital idea for an Android-side implementation at #29, feedback is welcome