Parsing large longs instead of crashing on Long.parseLong("0xffffffff")

[paulpv]

No description provided.

[davidgyoung]

This offers a partial fix to this issue: #173

A problem with this solution is that it changes the behavior of the library for identifier fields that are 6 bytes long (e.g. Eddystone-UID instance identifier fields) which are supposed to be converted to a string as hex (e.g. "0x010203040506"). Because this behavior is published, this would essentially be a breaking API change.

An alternate solution to this would be to not use the string when converting to the long values for the data fields but instead using the underlying byte array.

[paulpv]

@davidgyoung Understood.
Would it perhaps be worth adding a flag or parameter to interpret the number as hex or decimal?

[davidgyoung]

The Identifier class stores as a byte array internally, and utility methods allow conversion to various formats. The default string conversion, however needs to remain consistent.