Xcode 9

[Bernd Fröhlich]

I Updated Xcode to version 9 and now Xojo (2017R2.1) can´t run my iOS project.
The green button is dimmed and when i mouse over it, it says "Xcode and required command line tools are not installed" (even though Xcode is running).

Do I have to reinstall an older version of Xcode or is there a way to make it work with the new version?

Greetings from Germany,
Bernd Fröhlich


To unsubscribe, email ***@xojo.com

[Christian Schmitz]

Post by Bernd Fröhlich
I Updated Xcode to version 9 and now Xojo (2017R2.1) can´t run my iOS project.
The green button is dimmed and when i mouse over it, it says "Xcode and required command line tools are not installed" (even though Xcode is running).

You may want to check the threads about this on the Xojo forum.

Xcode 9 is not supported yet.

Sincerely
Christian

[Christian Schmitz]

Post by Bernd Fröhlich
I Updated Xcode to version 9 and now Xojo (2017R2.1) can´t run my iOS project.
The green button is dimmed and when i mouse over it, it says "Xcode and required command line tools are not installed" (even though Xcode is running).

You may want to check the threads about this on the Xojo forum.

Xcode 9 is not supported yet.

Sincerely
Christian

[Richard Gorbutt]

You will need to download Xcode 8 again. There was a thread on the forums
about it. I think Xcode 9 no longer support 32 bit which is needed for
debugging. Apps are built 64 bit. I could be a little wrong here.

This was posted in the forum

Downloading and Installing Xcode 9 from apple store. Rename "Xcode" to
"Xcode9" in the program folder. Locking into my development account. Run
and tested the simulator etc. everything simes to be working fine!

Then I have downloaded Xcode 8.3.3 from
https://developer.apple.com/download/more/
<https://developer.apple.com/download/more/> . Opened it in the download
folder, and move it to the program folder under "Xcode". Then I have
Download the old simulator from inside the Xcode 8.3.3. Locked into my
developer account. Tested Xcode with old simulator. Testet an everything
simes to be working fine!

Then I have reinstalled Xojo 2.1. Testet and everything sims to be working.

I Updated Xcode to version 9 and now Xojo (2017R2.1) canÂŽt run my iOS
project.
The green button is dimmed and when i mouse over it, it says "Xcode and
required command line tools are not installed" (even though Xcode is
running).
Do I have to reinstall an older version of Xcode or is there a way to make
it work with the new version?
Greetings from Germany,
Bernd Fröhlich

To unsubscribe, email ***@xojo.com

[Bernd Fröhlich]

Post by Richard Gorbutt
You will need to download Xcode 8 again. There was a thread on the forums
about it. I think Xcode 9 no longer support 32 bit which is needed for
debugging. Apps are built 64 bit. I could be a little wrong here.
This was posted in the forum
Downloading and Installing Xcode 9 from apple store. Rename "Xcode" to
"Xcode9" in the program folder. Locking into my development account. Run
and tested the simulator etc. everything simes to be working fine!
Then I have downloaded Xcode 8.3.3 from
https://developer.apple.com/download/more/
<https://developer.apple.com/download/more/> . Opened it in the download
folder, and move it to the program folder under "Xcode". Then I have
Download the old simulator from inside the Xcode 8.3.3. Locked into my
developer account. Tested Xcode with old simulator. Testet an everything
simes to be working fine!
Then I have reinstalled Xojo 2.1. Testet and everything sims to be working.

OK, thanks for the info.
I installed Xcode 8.3.3 again and all is well again (no need to reinstall Xojo 2.1).

While we´re at it: any known problems with High Sierra so far?

Greetings from Germany,
Bernd Fröhlich


To unsubscribe, email ***@xojo.com

[Tim Jones]

Post by Bernd Fröhlich
While we´re at it: any known problems with High Sierra so far?

Hi Bernd,

I've been operating on 10.13 for some time now and aside from the caveat that you MUST be case aware when accessing files if you're using an all SSD Mac (APFS), everything has worked as well as expected.

Tim



To unsubscribe, email ***@xojo.com

[Bernd Fröhlich]

Post by Tim Jones
I've been operating on 10.13 for some time now and aside from the caveat that you MUST be case aware when accessing files if you're using an all SSD Mac (APFS), everything has worked as well as expected.

Yikes, that´s indeed good to know (I didn´t know it until now). Thank you.


To unsubscribe, email ***@xojo.com

[Jon Ogden]

Really? MacOS is now a case sensitive OS?

Sent from my iPhone

Post by Tim Jones

Post by Bernd Fröhlich
While we´re at it: any known problems with High Sierra so far?

Hi Bernd,
I've been operating on 10.13 for some time now and aside from the caveat that you MUST be case aware when accessing files if you're using an all SSD Mac (APFS), everything has worked as well as expected.
Tim

To unsubscribe, email ***@xojo.com

[Jerry Fritschle]

Post by Jon Ogden
Really? MacOS is now a case sensitive OS

I believe it is an issue of the filesystem (APFS) rather than the OS per se.

-----
"Drama is life with the dull bits cut out."
-Alfred Hitchcock

Jerry Fritschle
***@icloud.com






To unsubscribe, email ***@xojo.com

[Jon Ogden]

Post by Jerry Fritschle

Post by Jon Ogden
Really? MacOS is now a case sensitive OS

I believe it is an issue of the filesystem (APFS) rather than the OS per se.

Well, yes, but previously, you had the choice between a case sensitive and non-case sensitive system when formatting a drive. I’ve always loved the fact that Mac OS has had the option to not be case sensitive. What other nasty little surprises are under the hood?




To unsubscribe, email ***@xojo.com

[Bernd Fröhlich]

Post by Jon Ogden
Really? MacOS is now a case sensitive OS?

No, it´s not.
Just tested on my spare MacBook Air:
Upgraded it to High Sierra.
Format of the SSD is "APFS" now.
When I have a file "Test.rtf" I can not creat a file "test.rtf". The Finder tells me, that that name already exists.

Greetings from Germany,
Bernd Fröhlich


To unsubscribe, email ***@xojo.com

[Jon Ogden]

Post by Bernd Fröhlich

Post by Jon Ogden
Really? MacOS is now a case sensitive OS?

No, it´s not.
Upgraded it to High Sierra.
Format of the SSD is "APFS" now.
When I have a file "Test.rtf" I can not creat a file "test.rtf". The Finder tells me, that that name already exists.

Whew! What a relief. @Tim Jones - Did you set case sensitive on when you updated?



To unsubscribe, email ***@xojo.com

[Tim Jones]

Post by Bernd Fröhlich

Post by Jon Ogden
Really? MacOS is now a case sensitive OS?

No, it´s not.
Upgraded it to High Sierra.
Format of the SSD is "APFS" now.
When I have a file "Test.rtf" I can not creat a file "test.rtf". The Finder tells me, that that name already exists.

Nope installed fresh. And you only get case sensitive APFS if you're installing fresh and you don't have non-SSD attached.

Tim



To unsubscribe, email ***@xojo.com

[Jon Ogden]

Sent from my iPhone

Post by Tim Jones

Post by Bernd Fröhlich

Post by Jon Ogden
Really? MacOS is now a case sensitive OS?

No, it´s not.
Upgraded it to High Sierra.
Format of the SSD is "APFS" now.
When I have a file "Test.rtf" I can not creat a file "test.rtf". The Finder tells me, that that name already exists.

Nope installed fresh. And you only get case sensitive APFS if you're installing fresh and you don't have non-SSD attached.

That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??
To unsubscribe, email ***@xojo.com

[Bernd Fröhlich]

Post by Jon Ogden
That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??

It´s not a bug, it´s the same feature as with HFS+. You can choose what you want.

Here is the official answer:
<https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html>

"APFS, like HFS+, is case-sensitive on iOS and is available in case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default."

Greetings from Germany,
Bernd Fröhlich


To unsubscribe, email ***@xojo.com

[Tim Jones]

Post by Bernd Fröhlich

Post by Jon Ogden
That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??

Because the would have beaus coups issues updating a system where changing from case insensitive would result in probably file collisions during the upgrade. APFS as the default only on SSDs was always the plan as it was designed for the newer Mac systems - which are all SSD.

Post by Bernd Fröhlich
It´s not a bug, it´s the same feature as with HFS+. You can choose what you want.
<https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html>
"APFS, like HFS+, is case-sensitive on iOS and is available in case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default."

And that stand is a change from the original design of APFS - it was originally released as case-sensitive only. It was changed after major companies whined about how that would break there apps.

Coming from the Unix world (of over 34 years), we're used to case sensitive environments, so all of our apps check this regardless of what the filesystem allows. It really is the smarter way to handle a filesystem.

--
Tim



To unsubscribe, email ***@xojo.com

[Randy Young]

That logic sounds flawed. Going from case insensitive to case sensitive cannot result in a conflict since insensitive is the broader instance and would already have prevented the conflicts. I don't know the rationale for Apple to change but potential collisions cannot be it.

Post by Tim Jones

Post by Bernd Fröhlich

Post by Jon Ogden
That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??

Because the would have beaus coups issues updating a system where changing from case insensitive would result in probably file collisions during the upgrade. APFS as the default only on SSDs was always the plan as it was designed for the newer Mac systems - which are all SSD.

Post by Bernd Fröhlich
It´s not a bug, it´s the same feature as with HFS+. You can choose what you want.
<https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html>
"APFS, like HFS+, is case-sensitive on iOS and is available in case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default."

And that stand is a change from the original design of APFS - it was originally released as case-sensitive only. It was changed after major companies whined about how that would break there apps.
Coming from the Unix world (of over 34 years), we're used to case sensitive environments, so all of our apps check this regardless of what the filesystem allows. It really is the smarter way to handle a filesystem.
--
Tim

To unsubscribe, email ***@xojo.com

[Tim Jones]

Post by Randy Young
That logic sounds flawed. Going from case insensitive to case sensitive cannot result in a conflict since insensitive is the broader instance and would already have prevented the conflicts. I don't know the rationale for Apple to change but potential collisions cannot be it.

Apple's logic, not mine. It's right up there with a bug that could have been sorted in launchd with 2 lines of code (which I included in my bug report) that took them from 10.7.5 until 10.13 to resolve ...

Tim



To unsubscribe, email ***@xojo.com

[Markus Winter]

Post by Tim Jones
It's right up there with a bug that could have been sorted in launchd with 2 lines of code (which I included in my bug report) that took them from 10.7.5 until 10.13 to resolve ..

Sounds like anyone we know …?

;-P






To unsubscribe, email ***@xojo.com

[emile.a.schwarz]

Format a hard disk as Case Sensitive (CS), store some web pages, use it a while, copiy data from CD to CI a lot of time and come back here.

 

You will get conflicts as soon as in your web page (created with (CS) you have two files with nearly the same name; say Apple.png and ApplE.png, when you want to copy it in a Case Insensitive hard disk.

 




 

 

Message du 28/09/17 04:56
De : "Randy Young"
A : "Nug"
Objet : Re: Xcode 9
That logic sounds flawed. Going from case insensitive to case sensitive cannot result in a conflict since insensitive is the broader instance and would already have prevented the conflicts. I don't know the rationale for Apple to change but potential collisions cannot be it.

Post by Jon Ogden
That sounds like a bug. Why would they enforce case sensitivity only on fresh installs only on SSDs??

Because the would have beaus coups issues updating a system where changing from case insensitive would result in probably file collisions during the upgrade. APFS as the default only on SSDs was always the plan as it was designed for the newer Mac systems - which are all SSD.

ItÂŽs not a bug, itÂŽs the same feature as with HFS+. You can choose what you want.
"APFS, like HFS+, is case-sensitive on iOS and is available in case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default."

And that stand is a change from the original design of APFS - it was originally released as case-sensitive only. It was changed after major companies whined about how that would break there apps.
Coming from the Unix world (of over 34 years), we're used to case sensitive environments, so all of our apps check this regardless of what the filesystem allows. It really is the smarter way to handle a filesystem.
--
Tim

To unsubscribe, email ***@xojo.com

[Bernd Fröhlich]

Post by emile.a.schwarz
Format a hard disk as Case Sensitive (CS), store some web pages, use it a while, copiy data from CD to CI a lot of time and come back here.
You will get conflicts as soon as in your web page (created with (CS) you have two files with nearly the same name; say Apple.png and ApplE.png, when you want to copy it in a Case Insensitive hard disk.

It was the same with HFS+, so nothing new on that front.


To unsubscribe, email ***@xojo.com

[emile.a.schwarz]

Post by Bernd Fröhlich
It was the same with HFS+, so nothing new on that front.

I do not specify (HFS+ or APFS), but for some persons, there are news here.

 

 

Emile

 

Post by Bernd Fröhlich
Message du 28/09/17 09:23
De : "Bernd Fröhlich"
A : "Nug"
Objet : Re: Xcode 9

Post by emile.a.schwarz
Format a hard disk as Case Sensitive (CS), store some web pages, use it a while, copiy data from CD to CI a lot of time and come back here.
You will get conflicts as soon as in your web page (created with (CS) you have two files with nearly the same name; say Apple.png and ApplE.png, when you want to copy it in a Case Insensitive hard disk.

It was the same with HFS+, so nothing new on that front.

To unsubscribe, email ***@xojo.com

[Tim Jones]

Post by emile.a.schwarz

Post by Bernd Fröhlich
It was the same with HFS+, so nothing new on that front.

I do not specify (HFS+ or APFS), but for some persons, there are news here.

I was also surprised at the number of folks in the Forum discussion who didn't know there was an option.

Tim




To unsubscribe, email ***@xojo.com

[emile.a.schwarz]

It always be the case.

 

You do not know just because you always use the default values.

 

But this have some troubles: if you have external hard disks, you better backup its contents and reformat it Case Sensible.

 

Why ?

At data copy from / to both disks, you winn fall into
 two files with the same nase (the difference is in the Case Sensitive
) and macOS will not be able to write two files with the same name 


 

I experimented that.

 

Emile

 

Message du 26/09/17 21:31
De : "Jon Ogden"
A : "Nug"
Objet : Re: Xcode 9
Really? MacOS is now a case sensitive OS?
Sent from my iPhone

Post by Tim Jones

While weÂŽre at it: any known problems with High Sierra so far?

Hi Bernd,
I've been operating on 10.13 for some time now and aside from the caveat that you MUST be case aware when accessing files if you're using an all SSD Mac (APFS), everything has worked as well as expected.
Tim

To unsubscribe, email ***@xojo.com