Cannot change project icon on expo.dev

[olarcher]

Build/Submit details page URL

https://expo.dev/accounts/oliver.larcher/projects

Summary

I cannot find any option for changing the icon for a particular project on expo.dev. In the project settings menu, there is an option to change the display name under "Project display info", but not the icon. It appears that the icon is initially set when uploading a build with icon for the first time, but it is not updated then the app icon changes.

Managed or bare?

Managed

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 14.1.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.9.0 - /opt/homebrew/bin/node
      Yarn: 1.22.19 - /opt/homebrew/bin/yarn
      npm: 10.2.3 - /opt/homebrew/bin/npm
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0
    IDEs:
      Android Studio: 2022.2 AI-222.4459.24.2221.9862592
      Xcode: 15.0.1/15A507 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^49.0.0 => 49.0.6 
      react: 18.2.0 => 18.2.0 
      react-dom: 18.2.0 => 18.2.0 
      react-native: 0.72.3 => 0.72.3 
      react-native-web: ~0.19.6 => 0.19.7 
    npmGlobalPackages:
      eas-cli: 5.9.1
    Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK
✖ Check that packages match versions required by installed Expo SDK

Detailed check results:

Some dependencies are incompatible with the installed expo version:
  expo-dev-client@2.4.6 - expected version: ~2.4.12
  expo-updates@0.18.11 - expected version: ~0.18.17
  react-native@0.72.3 - expected version: 0.72.6
Your project may not work correctly until you install the correct versions of the packages.
Fix with: npx expo install --fix
Found outdated dependencies

Error output

No response

Reproducible demo or steps to reproduce from a blank project

Go to https://expo.dev/accounts/<ACCOUNT>/projects and try to change a project's icon.

[tylerhammer]

Any chance you figured this out? It's been driving me nuts for some time.

[olarcher]

No, unfortunately. I'm starting to wonder if changing the icon used to be an option that was later removed, as the icons I still see in my project list are the ones for projects I created over two years ago. It seems new projects don't get the app logo defined at first build time by default anymore.

[DavidAmyot]

+1 I can't find anywhere how to change the actual project icon on expo.dev. The actual app's icon is fine, but I just want to change the project icon on expo.dev and I can't find out how?

[chaadow]

+1

[bjarheim]

+1

[NicolasMarcinkowski]

+1

[JClackett]

any news about this? is there some way to manually upload one?

[joaomellogomes]

The same with me

[s00se]

Would really like the ability to change project icon from the web interface

[lletfrix]

+1

[eduardocesb]

+1

[stesvis]

Nothing yet?

[oliviercperrier]

+1

[mirague]

+1

[michaek]

@olarcher, you marked this as needs review last November. Based on the history here, this is a real problem with expo.dev that needs to be resolved, not just reviewed. It's very frustrating to see outdated and missing icons in the management UI despite multiple builds/deploys with updated app icons, and yet have no way to resolve it.

Edit: sorry, you're the original reporter. I'll at-message someone else!

Edit: @szdziedzic, I'm picking on you because you've merged in some PRs on this project, and I'm hoping you'll know whose attention to bring this to at Expo.

[szdziedzic]

Hi,

Thanks for highlighting this issue. We are aware that we are missing this capacity on our website, we are thinking of adding it in the future, but we currently don't have the engineering capacity to do that. Generally, we understand that it might be problematic and want to solve it, but I can't promise any ETA at the moment.

[michaek]

Thanks for the update - just knowing that it's not in indefinite limbo is helpful!

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[olarcher]

Still relevant.