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

"Onboarding failed to complete." #53

Closed
amagriz opened this issue May 20, 2024 · 10 comments
Closed

"Onboarding failed to complete." #53

amagriz opened this issue May 20, 2024 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@amagriz
Copy link

amagriz commented May 20, 2024

Describe the bug
When launching the app, after the initial stage of logging into Epic Games and inserting the generated code, the app immediately states "Onboarding failed to complete. The operation couldn't be completed. Bad CPU type in executable.

To Reproduce
Steps to reproduce the behavior:

  1. Open Mythic app
  2. Generate Epic Games code and insert into app and click Next
  3. See error

Expected behavior
To be logged into Epic Games and to continue on with the onboarding process.

Screenshots
Screenshot 2024-05-20 at 17 07 24

Mac (please complete the following information):
Model: MacBook Air Retina 2019
Operating System: Sonoma 14.5
App Version: 0.1.1

Additional context
This issue happened on 0.1 also, but previous issue logged by another user has been closed?

@amagriz amagriz added the bug Something isn't working label May 20, 2024
@asxrow66
Copy link
Member

Have you tried rolling back Mythic or reinstalling 0.1.1?

@pablopoep
Copy link

if i am right u using an intell chip cuzz it is M chips only so it wont work ig

@pablopoep
Copy link

it trys to install rossetta 2 but u got intel so no work
(it is not gonna be made of intel)

@asxrow66
Copy link
Member

i'm not sure if it works on intel but if you're on intel cpu, you should use bootcamp which is built into MacOS and has way better support for games and can run games with an anticheat

@vapidinfinity
Copy link
Member

Very strange issue, it's almost as if the python script that handles Mythic's epic integration is ARM-only, which I can't replicate by running it through Rosetta.
I'll work on a fix later this week.

@amagriz
Copy link
Author

amagriz commented May 21, 2024

Have you tried rolling back Mythic or reinstalling 0.1.1?

Yeah, I tried this a couple times.

if i am right u using an intell chip cuzz it is M chips only so it wont work ig

Oh, I didn't see anywhere that Intel chips weren't supported. Normally when this is the case, apps don't even launch on an Intel mac.

i'm not sure if it works on intel but if you're on intel cpu, you should use bootcamp which is built into MacOS and has way better support for games and can run games with an anticheat

Bootcamp is unfortunately only a workaround and not a true solution to this issue. I am aware it has much better support being that it is just Windows, but I would rather not use Windows, and I'm perfectly fine with the performance hit that comes from WINE use.

Very strange issue, it's almost as if the python script that handles Mythic's epic integration is ARM-only, which I can't replicate by running it through Rosetta. I'll work on a fix later this week.

Looking forward to a potential fix. I realised I can skip the Epic login part of the initial setup, so I am able to run the app and use all features minus the Epic integration for now.

@vapidinfinity
Copy link
Member

vapidinfinity commented May 21, 2024

okay, janky fix found
imma have to use pyinstaller to compile the python script for x86, that way x86 can run it natively, and ARM can use rosetta
apparently there's no way to compile for both CPU types w/o a more complex solution

@billchase2
Copy link

Same issue here. Is it indeed an Intel issue?

@pablopoep
Copy link

yes they say it in the discord

@jeremybosma
Copy link
Contributor

Duplicate of #36

@jeremybosma jeremybosma marked this as a duplicate of #36 May 31, 2024
@vapidinfinity vapidinfinity closed this as not planned Won't fix, can't repro, duplicate, stale Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants