Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS: No account for team "Y3MLDMF5L7" Signing Error #363

Open
tylergaw opened this issue Feb 12, 2019 · 5 comments · May be fixed by #460
Open

iOS: No account for team "Y3MLDMF5L7" Signing Error #363

tylergaw opened this issue Feb 12, 2019 · 5 comments · May be fixed by #460

Comments

@tylergaw
Copy link

Environment

  • macOS 10.13.6
  • Xcode 10.1
  • react-native-splash-screen 3.2.0

Issue

After a fresh install of react-native-splash-screen following the manual install instructions and a Build in Xcode, signing errors are reported in the Report Navigator of Xcode.

screenshot
Screenshot showing xcode error

The errors occur during "Repair target SplashScreen":

No "iOS Development" signing certificate matching team ID "Y3MLDMF5L7" with a private key was found.

That team ID is in the SplashScreen project here

I'm not sure yet if this is causing any issues with building to a devices, but wondering if there's any fix or workaround for it?

@Abhijeetjaiswalit
Copy link

getting same error.

@andreshsingh
Copy link

+1

@ibedwi
Copy link

ibedwi commented Apr 27, 2019

I also get the same error

@MemoryNoodles
Copy link

i am too

@AndreiCalazans
Copy link

You might not need this library, react-native docs has some tips on how you can get rid of the white flash. https://facebook.github.io/react-native/docs/running-on-device#pro-tips

If you still need to use this library you can fork it and sign it with a not expired iOS Developer account.

@namnm namnm linked a pull request Feb 19, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants