Many methods do not use `IExecuteWithSignature`, but fallbacks into the `IExecute` method
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 44
- Forks
- 4
- Avg merge
- 17h 38m
- Merged PRs (30d)
- 78
Description
In the last reflection, many methods do not use anymore IExecuteWithSignature, but fallbacks into the IExecute method reporting, as can be seen in the attached file (JNetReflector.txt), the following error:
Error: SignatureFromGenericString: signature not found for method getDip (Generic string: public boolean android.text.style.AbsoluteSizeSpan.getDip()) of class android.text.style.AbsoluteSizeSpan using public boolean android.text.style.AbsoluteSizeSpan.getDip() not found.
The code is able to work using the IExecute method, however an issue will be opened on JNet to check it.
Originally posted by @masesdevelopers in https://github.com/masesgroup/netdroid/issues/184#issuecomment-3334572953
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached JNetReflector.txt output and tracing the reflection path around IExecuteWithSignature and its fallback to IExecute. Use the reported android.text.style.AbsoluteSizeSpan.getDip() failure as the first case to investigate; done means the signature is handled through the intended path without the reported lookup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100