markmarijnissen/cordova-app-loader

Fall back to last working version

Open

#21 opened on Feb 19, 2015

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (656 stars) (137 forks)batch import
enhancementhelp wanted

Description

Hey :)

If an update fails, why not fall back to the last working version, instead of the bundled version? Wouldn't that be way better?

Contributor guide

Tech stack
javascript
Domain
mobile
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the update logic in the repository to understand how versions are stored. Look at the current fallback mechanism that uses the bundled version. Discuss with maintainers to define what constitutes the 'last working version' (e.g., previous successful update). Implement a fallback that stores the last successful version separately.