I test it on Vista. The air application is set as startup - checked. After restart or log in, application start and InvokeEvent.reason is "standard". What can I do. And I don't think that the problem is sdk version. SDK that I use provide me with class InvokeEventReason which has constant LOGIN. For those who will ask me about the SDK version enyway, it is flex_sdk_22.214.171.12483.
Not the same thing, but also wrong, is the folowing behavior (tested on Windows 7 and SDK 126.96.36.1990): on first launch, the value of InvokeEvent.reason is LOGIN, as it should.
If, however, I shutdown my AIR application, and start it again, manually, the value of InvokeEvent.reason is still LOGIN, while it should really be STANDARD.
Hasn't anyone tested such a simple workflow? Good God...
So, what could I do?
OK, I'm back with more on that issue: it only occurs when user logs off / logs on in place of restarting.
So, If I log off, and then log on, the InvokeEvent.reason will remain set to LOGIN for the rest of the Windows session. If, however, I restart the machine, and then logon, the InvokeEvent.reason property will behave as expected.
While I do agree that this is partially working, is stil not good enough for me...