People spend 90% of their life worrying about things which never happen.
Listen to some whale music and await the final release 
Tell that to Sam. The same thing happened with OSX10.10
De DP versions worked fine, the two following PB did not. And hey presto … Apple released the final version with the same ‘bug’ (as you call it) as the PB.
As Gavin pointed out - you never can be fast enough to see why this is happening.
[quote=172648:@Richard Summers]People spend 90% of their life worrying about things which never happen.
Listen to some whale music and await the final release :)[/quote]
Nooo We’re all doomed! start buying Swift programming books now!!! ; )
[quote=172567:@Christoph De Vocht]OK, this is consistent:
Compiling with Xojo 2015r1 in OSX10.10.2 -> results in apps that crashes when run in OSX10.10.3 BP - but they run fine in OSX10.10.2
Compiling with Xojo 2015r1 in OSX10.10.3 -> results in apps that work fine in OSX10.10.3 BP and OSX10.10.2
Any reason why this happens?[/quote]
Hi Christoph
I just built an app from a brand new project in 10.10.2 and ran it in both 10.10.2 and 10.10.3 without issue. Byte for byte, the built apps are identical. Can you try the same test with a new project?
I’ve found one issue with 10.10.3 developer preview that I haven’t encountered before – unexpected nil folderItems. For example, I fill out a popup menu with the names of files in a particular folder, something like this, where item is a folderItem:
if folder <> nil and folder.exists then
u = folder.count
for i = 1 to u
item = folder.Item(i)
In the past, item was always valid. In 10.10.3 it is sometimes nil. The fix is simple, trap for nil:
if item <> nil then
...code
end if
This is with 2014R2.1 (I can’t upgrade to 2015R1 because for some reason it crashes with a dylib I use).
@Jonathan Ashwell I’ve seen this before (10.7), I think it’s a permissions error. Checking for nil is the best way.
Swift appears to the language of the future, but it’s limited in capability at the moment (requiring you to also learn Objective-C and build ‘bridge’ objects to access functionality that’s not in Swift.
Also apart from the FSRefs removal, 32-Bit frameworks being removed, most of these bugs are also present when using Apple’s own languages.[quote=172648:@Richard Summers]People spend 90% of their life worrying about things which never happen.
Listen to some whale music and await the final release :)[/quote]
Trouble with this approach is, 10.10.3 ships and your applications don’t work anymore. A majority of users instantly blame your application and Apple then refunds any customer that complains. They leave shitty app reviews and are angry with you. Even though it’s not your fault.
Consider beta releases of development tools and OSes as a trip to the future, if your application doesn’t work, you have two choices.
#1 File bug reports, so that the vendor knows there’s an issue. Then pray that they fix it.
#2 File bug reports and then work on a way around it, assuming that they’ll not fix it.
Yosemite marks a new era (IMHO) where the only option you have to prevent customer backlash is number #2. Not a single bug that I filed during the DPS of Yosemite have been fixed. Some are cosmetic, some are because never tech replaces then system I was using and some are just downright stupid (like Save sheets that grow 22 pixels taller every time they’re shown or AppKit functionality that doesn’t work unless your bundle identifier is an exact camelCase match to the application name).
Right now, I am furious with Apple, I’m working on replacing a technology that I’ve used for years. Not because Apple have depreciated it, because they’ve abandoned it! It’s still there, but under Yosemite it’s so easy to break, I’ve filed bug reports, but according to an Apple engineer, they’ll never get fixed.
If this is a trend from Apple, that every 6 months we have to spend at least 1 month, making our applications work (again), then I need to consider changing my line of work. As a small independent developer, I only earn when new apps ship, and so far I’ve spent more time chasing Apple than developing a new application. Maybe I’m getting to old, and I should get out the kitchen before I set myself on fire.
I have downloaded the Public Beta and installed it on my testing machine, so far everything all my apps are working, including apps I haven’t updated since 2011.
However considering that Christophe and Lisandro Mulena are both having Xojo apps crash, it worries me. I did update the test machine from 10.10.3 DP to PB, so I’ll try a clean install, see if that makes any difference.
@Jonathan: this problem is not related to 10.10.3. Some customers were having the same problem last week. I don’t see how this can be a permission error but I will check. In my case this seems to be always the same folder that is making problems: user/Library/Mail/V2.
I had started filing bug reports about Windows 10 Tech Preview which is essentially the same situation as 10.10.3 Public Beta (except no crashes), but the response from Xojo was kind of freezing.
Pending an official post, I can only report what I was told about Windows 10 Tech Preview, that Xojo officially won’t support systems which have not been released. Kind of “bug off”. Pun intended, but fact remains.
I am kind of dismayed to see that Xojo engineers seem to request more information about the Mac OS X Public Beta, as if once again Windows had to be the lesser child. Even if as a developer who has about 20 apps in the MAS, I am extremely anxious to see a rapid solution to these crashes, preferably before the actual release.
I have not had customers complaints, yet, but am starting to monitor crashes in Itunes Connect.
[quote=172746:@Michel Bujardet]I had started filing bug reports about Windows 10 Tech Preview which is essentially the same situation as 10.10.3 Public Beta (except no crashes), but the response from Xojo was kind of freezing.
Pending an official post, I can only report what I was told about Windows 10 Tech Preview, that Xojo officially won’t support systems which have not been released. Kind of “bug off”. Pun intended, but fact remains.
I am kind of dismayed to see that Xojo engineers seem to request more information about the Mac OS X Public Beta, as if once again Windows had to be the lesser child. Even if as a developer who has about 20 apps in the MAS, I am extremely anxious to see a rapid solution to these crashes, preferably before the actual release.
I have not had customers complaints, yet, but am starting to monitor crashes in Itunes Connect.[/quote]
I assume it’s just because OS X may be just 1 Month from now and Win is further away.
Right, they’re completely different! This is just a software update for an existing OS and most Macs these days are set up to automatically download these updates. Windows 10 is a new OS and a fair while away yet.
I agree there is a sense of urgency here that commands action. If all the sudden every Mac OS X Xojo app stops working it will be even worse than the Quicktime issue of 2013.
That said, I still feel that all platforms targeted by Xojo should be treated equally.
The release date, I’m sure make a big difference, there’s also the attitude from the OS vendor.
MS care about backwards compatibility, Apple don’t care about it and nor do they care about third party dev tool vendors.
I would hazard a guess and say that most of us vocal members on the forum who target OS X, are probably selling apps. If we can’t do that, it would cause Xojo issues. Whereas; (IMHO) I think most who target Windows are targeting companies, who probably won’t upgrade to Windows 10, until Windows 13 is out.
Apple are constantly making life harder and harder for 3rd Party tool vendors.
Heh - at the time Windows 13 is out they’ll say “Maybe we should look at updating to Windows 10”
Then put it off for a year as they’ll still be finishing their roll out of Windows 7 
Indeed companies are quite conservative. When something works, why fix it. That said, not all developers cater to corporate, and there is a very large end Windows user base. Windows 10 will be a free upgrade for Windows 7 and 8.x users, so chances are the adoption rate will be high. To be fair, the technical situation is far more favorable than Yosemite ever was ; backward compatibility is not a legend, and I spotted few real issues, including stability of the OS itself.
That said, I do agree that Apple does not give a damn, and it is on us all to scramble and make our software work on their platform in time for the release.
I saw conservative individuals (one is a University CS Professor !, the second is in this industry for 20 years but never learns anything excepted when he is in a n month training curse)…
I worked at Apple France, years ago, and I never understand (then nor since) Apple ‘politics’.
BTW: I met yesterday an Apple Genius who knows about OS X and Macs (a youngster) ! Incredible !
Yesterday and today I received 8 mails in total that some of my apps crash in OSX10.10.3 PB :-/
Seeing Apple will very probably release 10.10.3 next week after the Apple event we are in for some fun times.
Xojo Inc isn’t paying any attention to the OSX10.10.3 PB but it would be very great if they do.
[quote=172904:@Christoph De Vocht]Yesterday and today I received 8 mails in total that some of my apps crash in OSX10.10.3 PB :-/
Seeing Apple will very probably release 10.10.3 next week after the Apple event we are in for some fun times.
Xojo Inc isn’t paying any attention to the OSX10.10.3 PB but it would be very great if they do.[/quote]
I guess they are responsible enough not to hope the bug will go by itself, but they are probably embarrassed to admit they do not have a solution yet. Or maybe their famous policy of not wanting to care about OS betas is coming back to burn their inconsequent behind. Admittedly, though, this is one of those unfortunate situations where Apple threw an envil at all of us with no notice, to hell with backward compatibility.
With the Quicktime issue back in 2013 it could be said that Apple gave XCode users all indications to alleviate the issue, so us martians using an esoteric development platform were simply not using the official tools. Today the 10.10.3 conundrum is hitting everybody. I have been to the App Dev forums and they are full of reports of crashes under ill born Yosie. Among apps that crash, Apple’s own Photos app :s
Next week will probably be one for the records in terms of support request and angry refund demands…
How can you know? Maybe they are busy finding the issue and fixing it?