I’m trying to get a working icon for push notifications but when I change the file and do another “expo publish” I get “No assets changed, skipped.” and don’t get a new .apk.
expo build:status still shows the same latest build (### 0)…
In order to have the notification change take effect, you need to build a new binary. There are certain things that publishing will not work for that you can read about here. We’re working on some tooling improvements to make this less confusing for users.
Actually, though this is working now I’m still confused by the fact that when I changed an image file the publish step said “No assets changed, skipped.”. It’s confusing if it didn’t actually skip the file and had uploaded it (which it must have done if a later build did indeed add it to the generated apk).
Is it that the "No assets changed, skipped.” message refers to assets explicitly referenced in .js files rather than those referenced by the app.json’s assetBundlePatterns? Mine seems to be set to include everything but is this just the default perhaps?
So if it is only referenced in the app.json notification field then a change won’t be picked up?
I had earlier added a dummy require(‘./assets/images/notification.png’) into my App.json AppLoading startAsync but wasn’t sure if it needed to be used. Yet even if it is I still get the “No assets changed, skipped.” message.