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.

Sign up for GitHub

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

Jump to bottom

Tesla tunes will not download on Mac OS X 10.10.5 so latest version #15

Open
jamesbollan opened this issue Feb 11, 2018 · 42 comments
Open

Tesla tunes will not download on Mac OS X 10.10.5 so latest version #15

jamesbollan opened this issue Feb 11, 2018 · 42 comments
Assignees
@tattwamasi
Labels
bug

Comments

@jamesbollan
Copy link

Error message says TeslaTunes cannot be opened check with developer it will work with this OS X version

I know it does and have changed all settings to ensure it can be downloaded and opened as well as ensured latest version of OS. Help please
@tattwamasi
Copy link
Owner

Hi,
I haven’t looked at the code for a long time and haven’t even had to run the app lately, so I haven’t been checking to see how compatibility is holding up with newer os releases. I’ll take a look.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 11, 2018 via email

@tattwamasi
Copy link
Owner

Is this on an older device perhaps? 10.10.5 is a Yosemite version first released in August 2015. The last security patch to it (still called 10.10.5) was July 2017.

I just tried the app on my system and it's running as usual - but this system is running High Sierra, 10.13 (10.13.4 beta actually, but it's working on it fine).
I don't have any system still running with Yosemite on it. Before spending a lot of time trying to set one up to check things, can we get a little more info from you?

What is the exact error message (screenshot would be great)? What is the version of TeslaTunes from its "about" menu? You wrote like you had it working, then it stopped - could you elaborate? What changed?

Thanks. Happy to try to help figure it out with you, just would appreciate a little more background.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@tattwamasi
Copy link
Owner

There's no screenshot that made it into the issue. Should be able to attach it to this issue though.

Did you try taking the actual app from the unzipped file, putting it in applications, and then on your first time launching it actually right click (or control click, two finger tap, etc.) and choose open from the popup menu.

If it's a gatekeeper setting due to the app not being from the App Store, that should let it open. Since I can't (yet) see the error message, this is just guessing though.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@tattwamasi
Copy link
Owner

Did you try the open from the pop up menu rather than double click? Depending on gatekeeper settings, that may be needed for the first (and only the first) launch.

Your attachments aren’t showing up here. Should just be able to drag and drop the file or click select at the bottom of the box where you type your comment, like this....
1af0c6b5-f64b-4f3e-9b55-ee367c935cc9

Wanted to try an attachment myself just to check they are still working

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 13, 2018 via email

@tattwamasi
Copy link
Owner

the open I meant has to be from a right click / control click / 2 finger tap on the file itself inside a finder window. Gatekeeper treats that special compared to double clicking or using file->open from the top menu.

I don't see the screenshot attachment still - I see the text [Image: Inline image 1] instead…
You are using the github website to do these comments and not email, right? I don't understand why the files aren't getting uploaded for you.

I did just redownload the app from the latest release and I did get a gatekeeper warning due to, I guess, my developer key changing since I last released this. Surprised me to see it as an issue, but I was able to open it anyway with the right click -> open method I described.

I also did look and see that I still had it set to work on machines as far back as 10.10 so I really suspect this is a gatekeeper thing for you. Worst case I can rebuild the app and post a new release just to refresh the code signing that gatekeeper is looking at, but hopefully you can figure out the attach files thing and show the screenshot or just carefully type it out, and when trying to launch the app, make sure you do the right click trick vs. just open from the file menu.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 14, 2018 via email

@tattwamasi
Copy link
Owner

tattwamasi commented Feb 15, 2018 •
edited
Loading

This is from you starting the copy in your downloads folder it looks like, from the command line (I presume so you can copy and paste the error message ).

I don't know what to say at this stage. I don't get those messages from either my computer or from a separate non-dev test computer. They act (mostly*) as I expect. I'd suggest you do the following before giving up (mostly a rehash of earlier stuff, I know, but worth it to start from scratch as a last resort).

  1. Delete any of the TeslaTunes zips and apps already downloaded.

  2. Download from the latest release link, or from the top of the release tab of this project - this github repo should be the only source for an install. https://github.com/tattwamasi/TeslaTunes/releases/latest

  3. expand the zip file; drag the app to your applications folder. Do not try to run it from the downloads folder. Do not double-click it in the app folder either at this point. If for some reason you did double-click it and you have your Gatekeeper settings set to something besides wide open (and you shouldn't have it set to wide open - don't do that 😉 ) then I'd expect you would get a warning like this (the actual wording will depend on what your gatekeeper settings are - let me know if the window says something different or looks completely different):

gatekeeper message

Instead, in the Applications folder, hold down control and click the TeslaTunes.app file, and a popup menu should appear with open as the first line. Choose open. [note: you must do it from the popup menu - it triggers things differently than choosing open from the top-of-the-screen menu]
Another gatekeeper warning window will pop up that looks similar to the last message, but gives you the option to run it anyway:

gatekeeper shift open

If you click open, then the app should run, and from now on, it can just be started normally with a double click or whatever.

If you do each step of this and something different happens, tell me what and when (and figure out how to attach the screenshots 😄

—————-

* the mostly above is because I am surprised it is saying an "unidentified" developer. It should say my name. I was suspicious, but when I do a signature check on the fresh download it does show my unaltered, correct sig. I don't really know but suspect that apple just isn't finding my old key. Running the system policy check tool does show it is signed by me:

[rob@Noyce-2 Downloads]$ spctl -a -t exec -vv TeslaTunes\ 2.app
TeslaTunes 2.app: accepted
origin=Mac Developer: Rob Arnold (YUF2XVSDMC)
[rob@Noyce-2 Downloads]$ spctl -a -t exec -vv /Applications/TeslaTunes.app
/Applications/TeslaTunes.app: accepted
origin=Mac Developer: Rob Arnold (YUF2XVSDMC)

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@tattwamasi
Copy link
Owner

That sucks. Had hoped that'd get you going.

I asked earlier if you were using the github interface to post these comments, vs. using email. Seems like you are using email. Please try to attach the screenshot from the issue tracker using the instructions at the bottom of the area you type in. #15

After doing the attach in the web page, you should be able to click the preview tab and see the attachments in the page preview.

Is the message the same as what you pasted from the command line? If so I've never seen a pop up error message like that. I'm going to look at repackaging and resigning the app to refresh all the code signing stuff in the hopes that that will help you, but I'd really still like to see the screenshots.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@jamesbollan
Copy link
Author

screenshot 2018-02-13 10 10 34

@jamesbollan jamesbollan reopened this Feb 15, 2018
@jamesbollan
Copy link
Author

screenshot 2018-02-13 10 10 34

@jamesbollan
Copy link
Author

Hopefully you can see this ok

@tattwamasi
Copy link
Owner

Yeah I can finally see it - cool 😁

The error message still seems like you are trying it from an app on your desktop rather than in your applications folder? There is a "new" (not so new anymore) gatekeeper feature that activates when the app is being run from somewhere other than Applications.

I don't know if this could be causing an issue or not, but is why I specified moving the app to applications in my list of steps. Had the app managed to launch, it would have offered to move itself to applications for you to avoid other issues - but it didn't get that far.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 15, 2018 via email

@tattwamasi
Copy link
Owner

I don't get it either since the errors you posted are not referring to the app in the Applications directory, but instead looking on your desktop (and the earlier messages you posted were looking in your Downloads folder). I'm making a new one-off version for you to try, but you have to make sure there aren't old copies laying around in downloads and desktop, etc., just the one we are trying in applications. Maybe you can make sure of that while I get this version packaged up.

@tattwamasi
Copy link
Owner

You can try this version. I recreated it with a non-expired dev key so if that was the issue, this should get past it. If that's the issue, no clue why you are seeing it vs. anyone else. If we see the same problem with this one, no clue what the issue is but at least we'll know something it's not.
TeslaTunes_1.2.6-3-g62a5a4b.zip

@tattwamasi
Copy link
Owner

Any update?

@jamesbollan
Copy link
Author

jamesbollan commented Feb 19, 2018 via email

@tattwamasi
Copy link
Owner

You tried the version I linked into the comment a couple comments up from this one?

@jamesbollan
Copy link
Author

jamesbollan commented Feb 19, 2018 via email

@tattwamasi
Copy link
Owner

And it worked? Acted the same?

@jamesbollan
Copy link
Author

jamesbollan commented Feb 20, 2018 via email

@tattwamasi
Copy link
Owner

Interesting. I think I found the issue actually. It'll take me a bit to confirm and I'll attach a new release here to test out, but basically I think the issue is that 10.10.5 is old (I've wondered why you aren't upgrading, but I assume you have your reasons) and that the 3rd party libraries I use for the tags, etc. in the music files weren't by default built to maintain support back that far.

At some point when I did a new release, since they weren't specifically told to keep supporting 10.10, they built in a way that silently dropped that support. I should be able to rebuild them with 10.10 support, I just need to figure out how best to do it.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 20, 2018 via email

@tattwamasi
Copy link
Owner

You are on the latest for the 10.10 (Yosemite) releases. You could update to Sierra or High Sierra though at some point (hopefully after we’ve got this fixed and tested though).

Now that I have a clue about what’s going on, it’ll be kind of nice to fix this in case anyone else is stuck on the OS X 10.10 series.

One day you might want to look at updating to High Sierra (or Sierra) if there’s no specific reason not to. No releases have been bug free, and Apple should improve that trend, but it’s been out for a while now and has had several updates to fix things, improve security, etc. since launch.

Your call of course, and like I mentioned, would be nice to get this fixed first so I know it’ll work with Yosemite (10.10).

@tattwamasi
Copy link
Owner

Try this one. No promises, but let me know what, if anything, works differently.
If this works, I'll need to update the real release.

TeslaTunes_1.2.6-4-g6237472.zip

@jamesbollan
Copy link
Author

jamesbollan commented Feb 20, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 20, 2018 via email

@jamesbollan
Copy link
Author

jamesbollan commented Feb 21, 2018 via email

@tattwamasi
Copy link
Owner

That's great. Feel free to keep using that version.

I'll update this issue with the tech stuff in case any other dev gets caught by the same thing, make a new release for everyone else, and close this issue afterwards.

Thanks for taking the time to report and test things.

@jamesbollan
Copy link
Author

jamesbollan commented Feb 21, 2018 via email

@tattwamasi tattwamasi added the bug label Apr 30, 2018
@tattwamasi tattwamasi self-assigned this Apr 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tattwamasi tattwamasi

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tattwamasi @jamesbollan