0

If my references do not resolve after repeated compilation, and I have correctly placed the \label{} commands, what else should I consider?

  • I originally was adding this to the linked question but @Schweinebacke insisted that despite the same overall problem, it deserved a separate question because it was not the same specific issue. – Steven C. Howell Jul 1 '17 at 12:52
  • 2
    Please help us help you and add a minimal working example (MWE) that illustrates your problem. Reproducing the problem and finding out what the issue is will be much easier when we see compilable code, starting with \documentclass{...} and ending with \end{document}. – Heiko Oberdiek Jul 1 '17 at 12:54
  • @HeikoOberdiek I would not have been able to create a MWE until after solving the issue b/c I did not know where the issue was coming from. – Steven C. Howell Jul 1 '17 at 13:16
  • @Schweinebacke While I realize these linked post (or the one marked as being an exact duplicate) when I searched the problem I had both on StackExchange and Google, none of these came up. The problem I had was the references did not resolve. I did not think to check the interaction of hyperref and cleveref. These other posts only seem useful after you know what the problem is. – Steven C. Howell Jul 1 '17 at 13:19
0

Check if you are importing both hyperref and cleveref. In this case, I found I had to import cleveref second in order for the \cref references to resolve. This blog post introducing cleveref has the following warning at the top of the page:

"Warning: cleveref has to be loaded after hyerref!"

Not the answer you're looking for? Browse other questions tagged or ask your own question.