The difference between the ASDM-ACL and your CLI-ACL is keyword 'host'. Without 'host', the destination more or less become network ID/subnet instead of single host. That's why your second ACL works.
But I think you can refresh the ASDM so that it will take the latest config updated via the CLI.
Normally, when you create the ACL, the destination is specificed as host IP or object name (if you defined name for that IP 220.127.116.11). Additionally, the netmask of 255.255.255.255 will also determine whether the destination is a single host or network ID. If this is correctly done, then you're not doing anything wrong.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...