There is an issue when creating icon sets that the “Find” icon is not being submitted correctly. I never had an issue before and only has arisen over the past few weeks. It appears, on the preview screens, that your image for the “Find” icon has been applied. However, during the review process, Samsung has rejected all my icon sets for the same reason, a missing “Find” icon. There is obviously a glitch somewhere which is specifcally based on this icon. Again, I never had an issue before, this has only started to appear now and it’s very frustrating.
Please assist!
I wonder if it’s because the Find icon we design in the tool is not used on any A15 device?
I reported it months ago but still not fixed.
1 Like
Interesting. I have had 4 icon sets rejected all because of the same issue. I wonder if you specifcally remove A15 from the device list if the app would then be approved?
Here’s a screen shot showing all icons themed except the Find icon, but it’s in the tool… Which is actually funny because it’s a mandatory icon in themes but it’s not used on a phone 
I don’t think you can remove A15 devices but you can build the icons using A14 in the tool and just submit that binary. They may still try to test on A15 though unless you tell them not to in the comments.
The A14 binary will still work on all devices.
Or open a ticket.
1 Like
I reported at the beginning of February that the Find icon doesn’t show on phones, and it’s still not fixed. There is nothing you can do.
Flood the help desk with tickets, others are getting these rejections too and it’s ridiculous, especially because they are approving some and rejecting others.
1 Like
I opened a ticket but apparently I did not include all files they required so I had to resubmit. I am still waiting for an answer.
At this point, 6 icon sets have been rejected by them all because of this same “Find” icon issue. Obviously there is a problem lol Samsung is slow for any resolution so not holding my breath. If/when I receive an answer, I will update.
In the meantime, keep sending tickets, they need to see how widespread this problem is.
They’ve had 4 months since I told them this was a problem and still not fixed. It is amazing the number of bugs the app developers create. They will probably have it done for One Ui 8.
