Ask for time to process their feedback and schedule time days later to go over their feedback so that you can make sure that you absorb all the information provided. This will give a cooling off period and prevent emotional responses.

You may want to write down specific questions to ask as you process their report/feedback. Additionally, practice thoughtful responses that are not defensive but clarifying so that you get the most from the feedback and or clarifications.

Avoid the word "you" when referring to the developer who is doing the critique especially if you are taking issue with something that was reported. Instead, frame statements in a non confrontational manner, such as "I recognize the feedback given to mean that it may be better......". Or "for clarification, I could use some clarification for the statement/belief/finding.......". "I believe that their has been a misunderstanding/misconception when it was reported that....."

Such practiced statements will remove the defensiveness/blaming that can naturally occur when someone is critiquing something that we have worked so hard on. Time and practice can make this a good exercise for all concerned and avoid it becoming nothing more than what appears to be an attack on work that you were involved in creating.

Hope this helps.