Found out the issue. I jumped into this app midway and recently found out that the previous devs ejected out of expo and decided to undo that ejection. I came along and updated expo to 37 and started having this icon issue only on ios builds. We still had the iOS and Android directories within our app directory. Brent Vatne over at expo’s github page helped me solve this issue by deleting these directories and rebuild, which worked for me. His response was…
some context on why this is happening with ios and android directories present:
- we recently released support for expo-updates in bare react-native apps
- expo-cli needs some way to know if it should publish for a bare app or for usage in expo client / a standalone app built by expo build service
- so we look for ios and android directories to guess that
- then we set the target flag accordingly, so expo publish --target bare is the default if you have ios and android directories, otherwise it’s expo publish --target managed
we should let people know what target is being used explicitly in the publish output to be more clear about this
Hope this help anyone with similar issues with SDK37!