Hi, I have recently upgraded unity to 2019.4.37 and then realized “Debug.LogException()” throws exception which it mustn’t… It was working properly till I upgrade so I want to inform the developers… I expect a confirmation whether or not you are aware of it…
Post the line of code your using and the error.
it is irrelevant it has nothing to do with my code the behaviour of this method does not throw exception in normal case just writes on the console… But now it stops the player which means throws exception rather than just write it… when I remove it there is no problem…
Code dependant or not, it’s an old Unity version and such a vital piece of kit is bound to have been reported by someone else and then fixed. Either update your Unity version or send the line of code and error to confirm the problem.
You should not talk about the things you do not know… it’s upgraded from 2019.4.35 to 2019.4.37 and new version has been released just one week ago so it is broken with the new release it’s quite possible that no one has reported yet…
I expect the confirmation from developers not from you I don’t have time for chit-chat so mind your business…
Is this forum not that active?
I want to create a bug report but last time when I created one they have respond after 2 months which is not reasonable at all… Come on there should be some developers here right?
As I’m sure you can see, it’s extremely active.
Maybe the fact that you’re being rude/insistent is putting people off replying. I’m not sure who the devs are that you want an answer from.
If you don’t produce a bug report, there’s no magic to fix it for you. I had a quick search internally and I can see no mention of this so a bug report is the only way to go really.
If you want someone here to help you, then you need to provide some more information. A callstack in the very least might be useful.
2 Likes
Just for a sanity check I went ahead and loaded up a new 2019.4.37 project and used Debug.LogException().
void Start()
{
Debug.LogException(new System.Exception("foo"));
}
And the only exception I got was the expected behavior for LogException()
If you’re getting a different error to what you’re expecting LogException() to produce, please show us the line of code, and the error you’re seeing.
First of all I’m not a rude person but busy I see people always they do not read even what I say they just demand information and it is tiring after a while… and he says “update unity” really? like we were not smart enough to figure this out by ourself… I’m a professional programmer even with minor upgrades we have such problems as you can see so as company policy we upgrade the unity version every second year to minimize “upgrade bugs” because we do not have small projects… now lets focus on the problem at hand, there is no problem with the code and the problem is not the message… It pauses unity player which is not expected as you can see, it should write the exception not throw the exception (not pause the player) in normal case but with the upgrade it is broken and when I remove the line there is no problem the player does not stop as I said before in my second reply but you still ask me the exception message obviously you didn’t understand my question neither, or you don’t know how “Debug.LogException()” works because "the message is not the problem it should just log the exception not throw (not stop the player) Could I make it clear now?
Debug.LogException() Here is the unity documentation for the func…
When it comes to bug report as I said before since it takes too long to get reply, my policy is always asking here and if the bug is already a known issue then just wait for the fix otherwise If I can’t find a workaround then create a bug report… This way it is much much faster…
Thanks for your reply…
Alright guys, I have fixed the problem right now 
by checking the docs of the func I have noticed there is a message at the end which I have missed says “Note that this pauses the editor when ‘Error Pause’ is enabled.” which is a button on the console tabs and that was the problem it is enabled somehow and I have no idea how… I was thinking it is caused by upgrade so again wrong perception… And that is why I write on the forum first to be sure whether it is a bug or not… Clearly a good policy… Anyway, hopefully this can be useful for someone who stumbles upon this problem, I could not have guess that even after a million times because I have never used that button before… after 4 years of unity development, it is very strange that I find new things…
I never said you were a rude person by nature but you were being rude/impatient on these forums no matter what you say.
Glad you figured it out though.
Now, when I check my post again, obviously my first post is ambiguous and it can cause a confusion about the problem agreed but my reply is pretty clear and he still asks the code somehow like you did obviously you do not read carefully guys and If someone does not have enough information should not talk about it… it is not helpful and consume more time but anyway I may have overreact a little but he deserved a portion of it by giving me orders such as " dependant or not send your code", “update unity” etc. and you do not find this rude somehow… whoever talks to me in that tone will get the same answer, it is not rudeness it is an answer… I don’t come to these forums to argue and I have never argued before so If you do not push this argument forward it’ll be better and I won’t reply anymore anyway… Time is much more important to waste with arguments…
Good luck you all…