Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

No console on latest public build (2906)
Started by RicardoGraca Aug 24 2016 03:55 AM

8 replies to this topic
console
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

RicardoGraca

[GLOBAL: userInfoPane.html]
RicardoGraca
  • Observer

  • 9 posts
  • Corona SDK

I just installed the latest public build which is 2016.2906 (2016.6.21) and the console doesn't open at all. I was using 2831 and the console was working perfectly fine.

 

Previously the console would just open at the same time as the Simulator/Project Selector, but now it doesn't. Selecting "Console" from the menu also doesn't open it.

 

I'm using MacOS 10.9.5, so is this an issue with this older version? I get these errors on the system's own console:

24/08/16 12:47:11,223 CoronaConsole[16870]: -[__NSCFString containsString:]: unrecognized selector sent to instance 0x7f9481410ec0
24/08/16 12:47:11,224 CoronaConsole[16870]: -[__NSCFString containsString:]: unrecognized selector sent to instance 0x7f9481410ec0
24/08/16 12:47:11,225 CoronaConsole[16870]: (
	0   CoreFoundation                      0x00007fff8e31625c __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x00007fff83c54e75 objc_exception_throw + 43
	2   CoreFoundation                      0x00007fff8e31912d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
	3   CoreFoundation                      0x00007fff8e274272 ___forwarding___ + 1010
	4   CoreFoundation                      0x00007fff8e273df8 _CF_forwarding_prep_0 + 120
	5   CoronaConsole                       0x0000000100214948 -[ConsoleWindowController handleStdoutNotification:] + 1192
	6   CoreFoundation                      0x00007fff8e2e4e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
	7   CoreFoundation                      0x00007fff8e1d882d _CFXNotificationPost + 2893
	8   Foundation                          0x00007fff85415dda -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
	9   Foundation                          0x00007fff8550ea70 _performFileHandleSource + 1548
	10  CoreFoundation                      0x00007fff8e2475b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	11  CoreFoundation                      0x00007fff8e238c62 __CFRunLoopDoSources0 + 242
	12  CoreFoundation                      0x00007fff8e2383ef __CFRunLoopRun + 831
	13  CoreFoundation                      0x00007fff8e237e75 CFRunLoopRunSpecific + 309
	14  HIToolbox                           0x00007fff8686ea0d RunCurrentEventLoopInMode + 226
	15  HIToolbox                           0x00007fff8686e7b7 ReceiveNextEventCommon + 479
	16  HIToolbox                           0x00007fff8686e5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
	17  AppKit                              0x00007fff8c72b24e _DPSNextEvent + 1434
	18  AppKit                              0x00007fff8c72a89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
	19  AppKit                              0x00007fff8c71e99c -[NSApplication run] + 553
	20  AppKit                              0x00007fff8c709783 NSApplicationMain + 940
	21  libdyld.dylib                       0x00007fff839d15fd start + 1
	22  ???                                 0x0000000000000001 0x0 + 1
)



[TOPIC: post.html]
#2

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,539 posts
  • Enterprise

I'll see if an Engineer can tell anything from this.

 

Rob



[TOPIC: post.html]
#3

RicardoGraca

[GLOBAL: userInfoPane.html]
RicardoGraca
  • Observer

  • 9 posts
  • Corona SDK

Thanks Rob.

 

I just installed the latest daily build (2933) and this one seems to work fine. The console opens up as expected.

 

One thing to note is that the installation of the public build didn't work very well. For starters it installed alongside the previous daily build instead of replacing it, and then after removing it and the previous daily build and reinstalling the public build alone there was no Corona icon on Launchpad, although I could still access Corona through Applications in Finder.



[TOPIC: post.html]
#4

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,539 posts
  • Enterprise

Quite a few developers like to have multiple versions of daily builds installed, so we installed them into folders with numbers. Installing a public build we just install into CoronaSDK.

 

If the shortcut on the dock is pointing to /Applications/CoronaSDK/... then you should be able to update the build with no impact to that launcher icon. Even removing the folder and installing a public build shouldn't impact that.

 

I do things a bit different. /Applications/CoronaSDK is whatever build I want to currently use. If I'm on a daily build and I've previously installed a public build I'll simply rename the public build to CoronaSDK.2096 and then rename the daily build to CoronaSDK and let my launcher icon do its thing.

 

Rob



[TOPIC: post.html]
#5

RicardoGraca

[GLOBAL: userInfoPane.html]
RicardoGraca
  • Observer

  • 9 posts
  • Corona SDK

Ok, I see the benefits of having multiple versions, but that doesn't explain why the latest public build would not create the Corona launcher in Launchpad. In fact I couldn't even see the CoronaSDK directory there. It was just visible in Finder by going to Applications. I could pin the icon to the dock after launching it from Applications, but it was still not visible in Launchpad.

 

I know this version of MacOS is not supported anymore, and I'm not even using it to do builds, just for development, so it's ok if you don't have an answer for this. I'll be upgrading to the latest version later this year anyway, but I just wanted to check if this was a known issue or if it was something wrong on my side.

 

In any case the latest daily build is back to working fine. It's just the public build that has problems.



[TOPIC: post.html]
#6

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,539 posts
  • Enterprise

I almost never use the launchpad. I keep the commonly used stuff in the dock  and use spotlight to search for things I use less common. If I don't remember an apps name and need to see the icons, I can open up the Applications folder and find what I'm looking for just as fast if not faster than launchpad.

 

But that's me.



[TOPIC: post.html]
#7

Perry Clarke

[GLOBAL: userInfoPane.html]
Perry Clarke
  • Moderator

  • 850 posts
  • Corona Staff

We fixed a crash on 10.9 in CoronaSDK 2016.2908 (and subsequent versions).  We don't support 10.9 but the issue was obvious and easy to fix so it seemed a pity to exclude that version of OS X gratuitously.  We do not test our products on 10.9 before release so it may stop working again.

 

We don't do anything special with respect to Launchpad.  To my knowledge, whatever the Finder does is what you get.  For me, on OS X 10.11.6, the Corona Simulator icon in Launchpad points at the latest Daily Build I just installed by dragging its folder to /Applications.



[TOPIC: post.html]
#8

RicardoGraca

[GLOBAL: userInfoPane.html]
RicardoGraca
  • Observer

  • 9 posts
  • Corona SDK

For me, on OS X 10.11.6, the Corona Simulator icon in Launchpad points at the latest Daily Build I just installed by dragging its folder to /Applications.

 

That's also what happens in my case, but this issue is about the Public Build, not the daily builds.



[TOPIC: post.html]
#9

Perry Clarke

[GLOBAL: userInfoPane.html]
Perry Clarke
  • Moderator

  • 850 posts
  • Corona Staff

The issue with Launchpad appears to be that it only pays attention to application bundle ids.  So when you removed the Public Release from Launchpad you actually removed the bundle id com.coronalabs.Corona_Simulator which used by all versions of the Simulator (or something like that, I'm having trouble reproducing exactly what you saw).

 

It's tempting to think of Launchpad as being a sort of "view" of /Applications but they're completely separate things that can easily get out of sync (the Finder tries to keep Launchpad up-to-date with changes to /Applications but apparently it's not an exact science).




[topic_controls]
[/topic_controls]