This is my first experience with using a pdf builder but I have been using github for maybe two years now and I have never experienced anything like this before.
Not only did the latest version stop working but, now previous versions that I checkout on github are no longer working either. In fact, I can go back even to before I begun editting the builder and it still is not working!
I am at a loss to what has happened!
Related
I've been running VS 2019 for awhile now with no problems. I've been working on the same 2 solutions for the last year with no problems. Friday I upgraded to the latest version (16.6.2) because VS suggested I should. As soon as I did that, breakpoints in any MVC views no longer function in my project.
I have gone through the standard checklist of the old "No symbols have been loaded for this document" message. I have confirmed that the PDB files are in the right place, that the DLL and PDBs are of the same version, etc. Everything is exactly the same setting-wise as its always been. Friday morning it worked.
I installed the latest update (v16.6.2) and now the same breakpoint I had working a few hours before no longer works. Within this same project I CAN set a breakpoint in a controller or other classes - it seems to only be the .cshtml pages that are the problem.
My assumption is that one of 2 things occurred here: either v16.6.2 introduced a new setting I need to change in order for this to work, or v16.6.2 broke it. I have scoured the webs looking for any settings changes in this release and have come up empty. I have done the standard machine restart and all that stuff. No dice there either.
Are there any other troubleshooting steps I have missed?
I built an electron app that allowed dragging files in, with a jQuery script that just takes some info from that (path) and adds an li to a list. That's it. It worked great.
Then I followed this guide, because the next step is to send that information to a python script that analyzes the files (maybe relevant: when installing zeroRPC I built from sources, didn't rely on the prebuilt fork that's available there).
Now I get this crazy bug where when I drag files into the app my mouse pointer changes to not-allowed and the drop event doesn't fire. It's so weird.
I don't have any code sample to give because I can't really tell which part is wrong. The only changes I've done are the ones in the guide I linked, and they have nothing to do with the front-end. I'm really confused by this. not-allowed? Why?
Well, as suspected, the issue had nothing to do with either the front end or the back end. None of my code, really. It turned out that since I needed to compile some stuff while preparing zeroRPC, I used powershell as an administrator,, and you can't drag files from user-run explorer into an admin-run electron app - which makes sense and is in fact an expected behavior (it just so happened that I encountered this after doing some work, causing me to think the problem was with something I changed in my code).
We are doing some work around sharing UI across apps, both entire views and also individual controls, so the structure we end up with is (on Android):
Android App
View (Activity + Layout) pulled in from a NuGet package
Control (Layout) pulled in from another NuGet package
So the app pulls in the view and the view pulls in the control.
The problem we’ve seen is that resource IDs defined in the control’s layout don’t end up in the Resource.designer.cs of the app such that when the app runs we see a crash when FindViewByID is called.
Interestingly we have implemented the above in three different apps, it works in two and not the other, so I’m left thinking it is ever a difference in the build config somewhere or its pure chance and we can’t rely on this pattern working.
Has anyone seen this before?
Update:
Having paid closer attention to the build output I can actually see warnings being generated for the missing controls:
Warning XA0106: Skipping MyControl.Resource.Id.myId. Please check that
your Nuget Package versions are compatible. (XA0106)
Old question I know, but in case anyone needs it:
I experienced very similar problems after updating to Xamarin.Forms v4.1.0.581479, and followed James Esh's comment above, and JimmyGarrido's response here to get a resolution: https://forums.xamarin.com/discussion/89661/a-lot-of-warnings-appear-in-a-new-empty-xamarin-forms-xaml-project
The simple answer in my case was to remove the PCLAppConfig Nuget package. There may be other packages in your project which were built using an old version of the Xamarin.Android.Support* packages. Unfortunately I haven't found a way of diagnosing which package specifically causes the problem, so updating, then removing and retesting one-by-one led me to the solution.
I have done lightweight versioning in my project, right now i have two versions and the current version is set to latest one(dataModel 2.xcdatamodel for example). I have followed every steps there in the apple document. But it's crashing every time because the old version is loading(found that after debugging, the new attributes are missing in the entity) after fresh installation.
If i switch back to old version and roll back to current version again then it's running fine. I have deleted the references and added it again but the result is same.
My source code is on git and its very annoying to do that extra effort every time. Please help me to solve this problem.
thanks :)
If you are 100% sure that the new version is loaded, it means that you created the new version, started the app, applied changes to the model, started the app again. To eliminate the possibility of it, just create the 3rd version based on the 2nd version and make it current active. Also make sure you have the automated lightweight migration implemented as per apple manual here
https://developer.apple.com/Library/ios/documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/vmLightweightMigration.html
I am not sure, i guess it is a git/svn problem. We had to work with different versions of Xcode from the very beginning of the project. Whenever we committed to the git, the git found a miss match of Xcode versions(for say i am working with Xcode 5.1 and my team mate working with Xcode 5.0.1, the project was initialised with Xcode 4.1) and set the current core data version to the very older one that is dataModel 1.xcdatamodel in my case. That's why the project was running fine in my side but when my team mate pulled my code from the git and tried to run in his side it crashed everytime because the version was set to older one by the git.
I got this from here. After following the instructions the problem is solved for now.
Thank you all. If you have any better solution please share.
I recently changed from developing iOS apps on a MacMini to a new MacBook Pro (2.2 GHz Intel Core i7). While working in XCode, I occasionally get pop-ups when the system is apparently trying to do an autosave and runs into a problem.
The pop-ups state "The document [filename] could not be autosaved. The file has been changed by another application. Click Save Anyway to keep your changes and save the changes made by the other application as a version, or click Revert to keep the changes from the other application and save your changes as a version."
Examples of the filename are: AppDelegate.m, MyLoginViewController.m. There shouldn't be anything else that is changing those files.
I can't do anything within XCode until I choose one of the options. Sometimes it seems like the system is trying to overwrite my newest code with an old version of my code, sometimes it seems like it is trying to save my newest code. So, sometimes Revert is what I need to do to keep my current version, and other times Save Anyway is what I need to do. However, sometimes, I can't tell what the system is trying to do and I choose the wrong option and lose hours of work.
This has happened numerous times over a span of three weeks.
I am using OS X 10.7.2 and XCode 4.2.1. The code is on my MacBook's hard drive.
Does anybody have any idea why this is happening?
Thank you.
This is a huge problem, and it looks like it's Lion's force-fed "file-versioning" that is destroying work.
I typed quite a bit of code into my source and saved it regularly (pretty much after every complete paragraph). Suddenly I couldn't find an entire section that I'd just written. I even did a project-wide search, in case I'd accidentally entered it in the wrong file. Suddenly Xcode raised a dialog saying it couldn't autosave the file because it had been modified externally. Did I want to "revert", or save what was in the editor?
In the several times I've seen this come up on two systems over the past few weeks, I've chosen to save what's in the editor, thinking that obviously it must be the most recent version. WRONG. I hit "Revert", and the block of code reappeared.
There is so much wrong here, it's hard to decide what's the most offensive.
Confirming that this happens on XCode 4.3.2 on an iMac running 10.7.4.
I have found that this bug may be related to having the same file open in more than one tab or window in XCode. If you carefully avoid ever having more than one window open on a given file at a time I think you can avoid this problem. However, it undermines the very useful ability to apple-click method names to navigate to the file that contains them.
This has cost me hours of original work and been the source of immense frustration. The derisive comments from others are simply inadequate.
I heard they had a complicated fix for it already at Apple, but unfortunately, it was "accidentally lost" and now they can't remember which files need what changes to make it work again. :-/