Replies: 1 comment 1 reply
-
It is important to understand how It is maintained (by default) in an The data portal flows I suspect that when the Android native code calls back into your app, that the code in your app isn't running on a child thread of the original parent, and so has no access to Because an Android app is basically just like any other smart client app, you might be able to create your own context manager that stores I still don't know for sure if this will work, but it is probably worth a try. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say I have a value that exists in the ClientContext:
Csla.ApplicationContext.ClientContext["TestKey"] = "Client Context Value";
When I access that value in shared code from a call initiated in shared code, that value exists. If I try to access that value from shared code in a call initiated in native code, it does not exist.
As an example, let's say there's a Firebase specific override that's initiated by the Firebase SDK. If I want to then make a call from that override (native), into shared code, using a static method in shared code, the ClientContext is missing the value.
Is this expected? Am I doing something wrong?
I've attached a sample of what I'm talking about in case it's not expected behavior and what I'm saying is hard to follow.
ClientContextTest.Mobile.zip
Beta Was this translation helpful? Give feedback.
All reactions