Odd caching behaviour in the native binary?

@d4h wrote:

We’re currently preparing an Ionic 4 application for iOS and Android release. Across both platforms I’ve observed this behaviour:

1. We use a custom component to fetch and display (basically figure > img) because our image API is programmatic. This component just calls a service to fetch the image and turn the blob into a URL.
2. Before the user shuts down the app, this works totally fine. It displays correctly.
3. After the user restarts the application, and older version of this component displays with a placeholder graphic.
4. All instances of this component use the same placeholder graphic.

At this point in time I have removed both the placeholder graphic and all references to it from our code. It appears that after the user restarts the application it shows the older component.

IMG_6A83CD7E1E8C-1.jpeg750×509 99.7 KB

In the screenshot above, a broken “image not found” graphic should show, not the placeholder. Steps to build application:

1. rm -rf www
2. ionic cordova platform rm ios && ionic cordova platform add ios
3. ionic cordova prepare ios (in this case)
4. Build in xcode.

It’s always the same pattern. New component before build, old component after. What the heck?

Posts: 1

Participants: 1

Read full topic