Answer
This can never work, by design — page numbers are only generated at the very final stage of PDF generation, after all visibility conditions have already been evaluated. At the point a condition is checked, the page number simply doesn't have a value yet, so a condition that references it can't behave as expected. Page-number-based visibility logic isn't achievable in Report Designer; you'd need a different approach (for example, a data-driven flag distinguishing the first record/section from the rest) to achieve a similar 'hide on the first occurrence' effect.