Unable to initialize Parse

[jcguarinpenaranda]

I am just starting with Parse and Unity, and I'm not able to initialize Parse.

I'm getting the following error:

I have a blank project, with the files:

Where ParseInit.cs is the script on which I am initializing Parse.

And here's the code for that file:

As you see, right now I am only logging to the debug console the ParseClient class, but I'm getting the error I mentioned above, which says that ParseClient is defined multiple times.

Do you know how it can be solved? Or why is this error showing up?

Thank you

Edit

My environment is MacOSX El Capitan, and my version of Unity is the 2017.1.0f3 Personal

[jcguarinpenaranda]

Fix

I had copied all the Parse-1.7.0 folder. To fix this, I replaced the whole folder with one of its subfolders.

Instead of importing Parse-1.7.0 I imported the Parse.Unity folder that was inside.

New problem

Now, after having imported the right folder, I have this very simple script copied from the docs:

After running it, I understand it should save an object to my database. Instead nothing happens.

Also, If I try to place the lines 20-23 in a separate file, I get an AggregateException

[jcguarinpenaranda]

I think this set of questions and answers may be valuable for other people that are starting with this SDK like me.

Fix 2

To fix the previous error, I had to go in Unity to Edit > Project Settings > Script Execution Order and set ParseInit.ts (The file where I initialize the Parse SDK) as the first script. Then ParseTest.ts as the second script, like this:

New Problem

Now that the AggregateException is not being thrown anymore, I still can't get the SDK to connect to my server, which is running in the localhost.

I tried adding and removing a / at the end of the Server string but nothing seems to work. I wrote the following script.

No Exceptions are thrown, and nothing is being logged to the console.

[montymxb]

We don't currently have active tests running against unity at this time. As such I'll have to take a look at this personally and let you know if there's something up.

[jcguarinpenaranda]

Thank you, please any help will be very appreciated

2017-12-20 18:50 GMT-05:00 Benjamin Wilson Friedman < notifications@github.com>:

We don't currently have active tests running against unity at this time. As such I'll have to take a look at this personally and let you know if there's something up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/parse-community/Parse-SDK-dotNET/issues/282#issuecomment-353216403, or mute the thread https://github.com/notifications/unsubscribe-auth/AG3gNR2VxxLkOjLtpW6shakdMJ8VdTuXks5tCZ07gaJpZM4RHxFF .

[jcguarinpenaranda]

Excuse me, I want to be proactive searching for a solution. What should I do? Is there anything I have to check again?, or maybe give you more details?

[montymxb]

@jcguarinpenaranda sorry to the lack of feedback. I have been working on putting together a method for building the current sdk, as it has differed significantly from the original instructions provided.

I've managed to get the basic components built for .NET, but I haven't started testing/building against Unity yet. That's the next thing in addition to Xamarin.

::edit:: I'll be updating the README and related pages with information on how to build the current SDK. The unity component will be part of this.

[jcguarinpenaranda]

Thank you so much, I will be waiting and if there's anything you need me to do in order to test this with Unity just tell me

[roddrift]

How does this even work? I cloned the git and put it in the assets folder and it is a mess - msbuild / xbuild produces nothing but errors - is parse a lost cause on Unity?

[montymxb]

@roddrift building with xbuild/msbuild on mac is currently non-functional. The same Dlls can be produced by building on windows, which I would recommend until that is resolved.

We're in the midst of some changes coming up for the sdk with potential support from additional contributors, from there we'll get some new Dlls, but serious Unity support may be coming later on. You can follow the discussion over in #274.

[roddrift]

Thanks @montymxb, appreciate the response.

[jcguarinpenaranda]

Hello, I just wanted to return to this issue as I have not been able to test with Unity again. Is there anything I can do to help? or, is everything working ok now?

[ycy1164656]

HI! Have you solved your problem? because now I have quite the same problem as yours. I can initialize parse, but I can't reach the server.The error message is "OtherCause" . So I can not know which step of initialize is wrong.

[jcguarinpenaranda]

Hello, are there any updates on this?

[jcguarinpenaranda]

Hello, has someone been able to solve this?

[TobiasPott]

@ycy1164656 @jcguarinpenaranda I assume you are using the parse version prior to the "Update Project" commit from alex on Dec. 22 2018?

I'm not sure if any changes regarding your issues were made before that commit but for now there is no direct support for Unity as a platform for the current state of the repository.

If it is very urgent I can check for my branch for Unity support on my fork of this repository. But that one is neither official nor tested beyond my own needs and will require Unity 2017 or newer. Let me know if that would be an option for you and I'll check which of my branches is the compatible and update it to the latest commit of the official repository.

[Fangh]

0. I use Unity 2018.3.0f1
1. I built the current master branch with Visual Studio 2017
2. I copy the "netstandard2.0" folder in my /assets folder
3. I Added the link.xml as written here : http://docs.parseplatform.org/unity/guide/#getting-started
4. I created a very simple script :

5. this is the error I get in my console :

[TobiasPott]

@Fangh Oh, I've never noticed the link.xml hint in the getting started until now. As I understand it's content it's used for the notification feature of Parse, unfortunately it refers to the old version of the Parse SDK for .NET and since the last repository update from alex @TheFanatr there is no built-in support for Unity at all and some parts of the .NET standard implementation do not work because of the way Unity compiles your code into assemblies and which one becomes the entry assembly of your application.

The code you are getting the exception from is affected by this. You may check out my working branch for Unity support which covers this issue and handles wrapping Unity version stuff for the access in parse. https://github.com/TobiasPott/Parse-SDK-dotNET/tree/feature/recode-unity-support Hint: It changes some other portions of the code to make it compatible with .NET standard applications and Unity applications and is not an official repository. It also does not yet include the notification feature. If you require the notification feature, I think you are stuck with an older version of the SDK unfortunately.

As alex stated in another thread, unity support is removed and will be brought back when a plugin structure, but I can not tell you when that will be ready.

If you try my current branch for unity support I'll please refer to any issues you have with a new thread on that repository instead. I'm happy to help and improve it aside from my own requirements.

[Fangh]

Thanks a lot for having taking time to show me a Unity version of the SDK you created. It will be so helpful for everyone. Maybe the admin of this repo should link your project in the readme so everyone using unity could use your SDK !

[TobiasPott]

I close this issue as most problems discussed here were either solved with the latest version available from the master branch or in the past by forked repositories. The latest version works with Unity on iOS and Android and several other target platforms, which may require additional configuration of the SDK using the mutators @TheFanatr has introduces with his pull request. Please take a look on the use-in-unity-client section of the readme.