I am using Unity Collab with my other team member to develop our game. After integrating the FireBGase Database asset package, I noticed that he had made a change to the project. I then pulled his changes and since then I have a conflict in Unity in my Plugins/Android folder.
Right-Clicking on any of the folders marked red presents me with an option to Resolve Conflicts. Regardless if I click Take theirs or Keep Mine - I am presented with an error stating "There are no valid assets to this operation on".
There are no files marked as having a conflict, only folders.
I am using the latest version of Unity 2017.3.1f1
I have yet been unable to find an answer for this issue.
Removing the Plugins and Androids file from Unity and adding them back in removed the conflicts on those two files - but there was still a conflict on the Assets folder.
In the end, I made a backup of my project and reverted the project to previous version on Collab.
I then add to readd the FireBase assets and copy back my changed code. A little bit of effort but it resolved the issue.
Related
I've recently upgraded my Unity project to 2021.2.3f1 on the new M1 16inch macbooks. Upon importing Firebase's SDK, I get the following error on async Tasks types:
It seems there's an ambiguity happening since it works fine without the SDK. Someone in the Firebase discord suggested that:
it's most likely related to the plugins folder dll files,
there should be a some dlls and a folder called net4xx,
if you remove (zip so you can restore it) the rogue dll files, it may fix it..
so only the net4x folder remains
Unfortunately the only net-something folder i've got in my project is in Assets>Parse>Plugins> and is called dotNet45, but it's the only one and there isn't any other net4-something folder anywhere in the project. Removing that dotNet45 folder creates lots of errors.
Someone knows what are the steps to fix this pls?
Thanks !
Actually I was almost there. They're not folders, its these two files that should be deleted:
Then it should be fixed !
I am using intl-tel-input in my project which I installed using npm. Every thing seems to work fine when I test using Firebase emulators but it stops working post deployment.
Upon checking the Sources tab in Chrome dev tools, I can see that the module is not properly included. (Pls check images) However, I am completely unable to figure out why. Please help!
Emulator Screenshot with the Telephone Input field working fine.
Screenshot taken post deployment with the Telephone input field broken.
Source File - intlTelInput.js located at /node_modules/intl-tel-input/build/css/intlTelInput.js
Source File - intlTelInput.css located at /node_modules/intl-tel-input/build/js/intlTelInput.css
By default Firebase ignores node_modules directories when deploying.
There are a few options you could use to resolve this.
Use a build tool like Rollup or Webpack to generate bundles that include node dependencies.
Copy required node_modules files to a different directory like assets and load them from there.
Update firebase.json to not ignore node_modules on deploy. Note that this will probably greatly increase the size of deployed applications if you have any number of node packages.
I took a fully working Xcode project and added a Podfile to it. After doing the pod install, opening the newly created workspace and trying to build, it no longer works. When I compile now I get errors from a couple system header files. For example, NSFetchRequestExpression.h tells me:
Attempting to use the forward class 'NSExpression' as superclass of 'NSFetchRequestExpression'
I manually went in and added $(inherited) to the front of the "Framework Search Paths" and "Other Linker Flags" build settings. Any ideas on what I need to change to make this work?
Finally figured this out. CocoaPods actually changes the way includes work. I had a core data entity called Time, which creates and NSManagedObject subclass called Time.h. When CocoaPods mucks with the header include search paths, suddenly the system files which asked for found my time file instead. I renamed that class (which I shouldn't have had to do!) and now everything works fine.
I am using Spring Source Tool Suite 2.8.1 to implement Spring applications.
I frequently get build errors because references are lost for no apparent reason. In Right-click project in Package Explorer->Properties->Java Build Path->Order and Export, I find projects sometimes are deselected. And often packages are gone in Right-click project in Package Explorer->Properties->Java Build Path->Deployment Assembly.
Having to reset these settings frequently is frustrating. Is there some way I can work around these problems?
I have tried to update STS to the latest version, but the upgrade process fails with incomprehensible error messages. I want to avoid a clean install because setting up the environment again would probably be a nightmare.
Now that I know this is a maven project and you are adding references yourself, this is making sense to me. STS 2.8.x was the last STS to ship with the legacy m2e (maven plugin for Eclipse). It did not recognize build path entries added manually (it likes to have complete control over the classpath). So, what is likely happening is that you are adding these classpath entries and then an update project operation gets kicked off automatically. This will have the effect of removing all of your extra classpath entries.
You are best off doing the following:
Updgrading STS
Or just upgrading your m2e component (you will have to first uninstall the old m2e, but this should be taken care of automatically from the discovery update page).
Or, just accept the fact that you can't manually change your classpath with the legacy m2e.
I need to store the release build of my Flash Builder (Flex) application in Subversion. When I try to add it to version control via Subclipse I get a warning telling me that I have asked to version control one or more resources that otherwise would have been ignored. Does anyone know why this is happening, and how I can get around it? I've gotten around this one time in the past by adding the build release's directory to the repository using another Subversion client, i.e. outside of Eclipse/Flash Builder, but when I rebuilt the release later I was unable to get Subclipse to see the changes between the base/head revisions and the new local versions of the build release files.
I realize that what I'm doing is non-standard and I suspect that there are default svn:ignore settings someplace which are causing this to happen, but I can't figure out where these are in order to modify/bypass them. Or maybe there's something else going on?
Thanks in advance for any insight and/or help with this issue.
This is an Eclipse-specific feature. Eclipse has a feature where files that are produced by compilers or generates inside Eclipse can be marked in Eclipse as "derived" resources. Eclipse team providers are supposed to ignore these files automatically. AFAIK, that is the only reason the feature exists.
So Subclipse still allows you to manually choose one of these files to version, but it warns you that you selected files that Eclipse said to ignore.
It is possible (but I have no idea) that Flex Builder has some setting to control whether or not it marks these files as derived.