New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrieve value from NSDictionary type #817
Comments
Hi @jibon57, if I understand correctly you are getting the proper NSDictionary by the delegate method but don't know how to access its values. According to Apple docs you can do it by calling |
@tdermendjiev Thanks for your reply & sorry for late response. I just tried as your suggestion like this:
Output:
It's null output. Any idea, in where I am doing mistake. Thanks |
@jibon57 PS: Just tested it and it prints: |
@tdermendjiev Thanks for your reply. I tried like bellow:
but same output:
Will you please share your working code? Thanks |
@jibon57 it appears that it's a nativescript-cli related issue with printing multiline console logs which we are currently working on. If you run the project from XCode you will be able to see the full logs and respectively the proper ones. Here is the code of the ViewController I used to reproduce the issue:
How were you able to print the whole NSDictionary output from your first comment - by running from XCode or from the CLI? P.S. Both |
@tdermendjiev Thank you so much !!! I thought my code has some problem that's why the output was null. I got the output of my first comment was from an older version of NativeScript. In XCode I am getting the complete output now. Now another questions... Can I use the value of |
@jibon57 you can use the |
@tdermendjiev Thanks for your reply. Will you please give some hints to use the value of |
In iOS the |
Hello
I am trying to implement one Native library in NativeScript (https://github.com/hackiftekhar/IQMediaPickerController#example-usage). The native code like this:
So, I am trying like this:
I am getting output like this:
But I can’t acccess the information. Thanks in advance.
The text was updated successfully, but these errors were encountered: