KITFORMA · EDITORIAL ANSWER
Why does an Object[] variable throw ArrayStoreException when it receives a number?
KitForma editorial guide. An array retains its runtime component type even when a wider reference points to it. The reference declaration does not rebuild the array.
Step-by-step answer
An array retains its runtime component type even when a wider reference points to it. The reference declaration does not rebuild the array.
If you need a genuinely mixed container, allocate
Object[] values = new Object[3]; rather than assigning a String array to Object[]. If the data must remain textual, keep String[] throughout and reject or explicitly format nontext input at the boundary. Inspect allocation sites when the failing assignment seems legal.
Verify a string and a numeric insertion against the intended container contract. Generic collections avoid this particular array covariance trap at compile time, but raw collections can still erase useful checks. This is a type-model issue, not an indication that the JVM has run out of array space.Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.