Presenting ViewController

ywangd

I can run the example block code (sorting function) from the documentation. My device is also a iPad Air 2.

The RPScreenRecorder did NOT run but it was due to a different error. The replaykit was not created successfully. The bundleWithPath_ method returned a None for me.

filippocld

Your error is there because you have iOS 8. ReplayKit is a framework of iOS 9.

Dunno about the example, maybe is some iOS 9 bug

@omz I was wrong, the line that crashes the app is line 14, where you call the handler. Anyway @on_main_thread crashes too for me. Remember i am on iPad Air 2 WiFi iOS 9 beta 5

filippocld

Ok, @omz in the meantime can you show me how to do with delegates, please? :-)
Would be much appreciated

omz

@filippocld said:

Ok, @omz in the meantime can you show me how to do with delegates, please? :-)
Would be much appreciated

Turns out that I was wrong about that. It's not possible to do this without blocks.

I don't really have any idea why this doesn't work for you, to be honest. I installed the latest beta directly from TestFlight (the exact same build you have) on an iPad Air 1 that has iOS 9 beta 5 installed, and it works just fine. I just can't think of a reason why it wouldn't work on an iPad Air 2 right now.

filippocld

Do you have a way to see my crash logs and maybe understand the problem?
I mean, it happens everytime i call an handler in every function, it shouldn't be so difficult.

omz

I only get aggregate crash reports, and they're delayed, so if you could send me one of yours, that might be helpful (Settings app → privacy → diagnostics & usage → diagnostics & usage data). I can't really promise that I can fix this though – as I've mentioned in the docs, the whole ObjCBlock feature is extremely experimental and relies on stuff that isn't really documented anywhere.

filippocld

I am currently having problems sith crash logs in iOS 9 beta 5, will send them later this week when beta 6 comes out.

Anyway i have a question.
Can you show me the simplest example of : "For blocks that don’t have a return value and no arguments, you can pass a Python function, and it’ll be converted to an ObjCBlock automatically."
? Still doing some testing and slowly understanding the mechanics

omz

Shortest example I can think of, though I don't really think it'll work for you if other blocks crash...

from objc_util import *
NSOperationQueue = ObjCClass('NSOperationQueue')
NSBlockOperation = ObjCClass('NSBlockOperation')

def foobar():
	print 'test'

q = NSOperationQueue.mainQueue()
op = NSBlockOperation.blockOperationWithBlock_(foobar)
q.addOperation_(op)

filippocld

I"m becoming crazy 😱. It crashed -.-
Until i can send you the logs i can only say you that block.invoke() crashes the app and that @on_main_thread does it too :-/

omz

Could anyone else with an iPad Air 2 test this?

Unfortunately I don't have such a device here. As the OS I'm testing on is the same, I can't think of anything else that could be different, apart from the actual hardware... I don't suppose your device is jailbroken? (don't think that's possible on iOS 9, but I don't really follow this closely).

The crashes with on_main_thread surprise/worry me more than those with blocks, to be honest. With the blocks, I know that what I'm doing is a total hack, but the on_main_thread stuff should be pretty standard, and uses documented APIs...

omz

What exactly is the problem with the crash reports btw?

filippocld

Device is not jailbroken, True statement( if it changes something)is off.
For the logs i cant find a Pythonista-date.log but i find LatestCrash-Pythonista and LatestCrash-Pythonista2, but they're both empty Screenshot

omz

@filippocld said:

True statement( if it changes something)is off.

What do you mean by this?

To be honest, I'm not sure the crash reports would help me very much anyway. It's very difficult to fix something that I can't reproduce at all myself. Usually, a crash report helps with reproducing issues, and then fixing them, but from what I've seen so far, I think the problem may be hardware-specific and just not reproducible on what I have here. I might need to get an iPad Air 2 myself, though I'm a bit reluctant to buy one now, given that there will probably be new iPads in less than 2 months...

filippocld

In Pythonista Settings there is an option called True statement, which i don't know what does, so i left it to No
For the @on_main_thread thing i remember that in the beta before the introduction of the blocks(160022) @on_main_thread was working fine.

Then in beta 160023 you changed something in on_main_thead that caused the crash

From the Beta Release notes of 160023: "on_main_thread()` should be reentrant now (which means that it's possible to nest calls that are executed to the main thread -- while this mostly worked before, there were cases in which it would result in corrupted return values)."

omz

That's very interesting information, thanks!

I think you mean the "True Divisison" setting – that shouldn't make a difference at all, it's just for the interactive console, and determines whether something like 5/2 evaluates to 2 or 2.5.

filippocld

Oh, then that's useful :-) thanks

omz

I just ordered an iPad Air 2 that I'll pick up later today. I'm curious if the issue is reproducible, though I'm really not sure if I can fix it, even if it is – it might be too low-level... In any case, it'll be useful to test the new split-screen stuff in iOS 9 as well...

filippocld

Good! Hope will fix both the crashes or at least one of them.
I am kinda angry when i make a iOS 9 api scripts(Replaykit,Search Apis,Touch id etc.) and cant use it because blocks crash and on main thread crashes too

omz

Okay, I have the new iPad set up for development, and it really seems like this is a hardware-specific issue. I can at least reproduce your crashes now... haven't really investigated this much further yet, just wanted to let you know that I don't really need crash reports anymore.

filippocld

Oh, thanks! Finally im not only the one with theese problems.
Looking forward for more infos.
Thanks in advance
Filippo