wequick/Small

Resources.getIdentifier 找不到资源

Open

#195 opened on Jul 5, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (5,028 stars) (1,123 forks)batch import
enhancementhelp wanted疑难杂症

Description

前提： lib.style 有资源 test_resource

lib.utils UIUtils.java 

    public static void testResource(Context context) {

        int c1 = context.getResources().
                getIdentifier("test_resource", "string", "net.wequick.example.small");
        int c2 = context.getResources().
                getIdentifier("test_resource", "string", "com.example.mysmall.lib.style");


        Toast.makeText(context, c1 + "   " + c2, Toast.LENGTH_SHORT).show();
        Toast.makeText(context, c1 + "   " +
                context.getResources().getResourceEntryName(c2), Toast.LENGTH_SHORT).show();
    }

现象： c1得不到资源id，c2可以。

期望： c1能得到资源id

项目中一个第三方库内部使用了这个方法，但是getIdentifier第三个参数它默认传的是context.getPackageName, 故找不到资源。

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Android developmentunderstanding of context and resources
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how the Android resource resolution works in the context of Small's plugin system. The issue shows that using `context.getPackageName()` for `getIdentifier` fails because the resource is in a library's package. Look at how Small loads resources and consider using the library's package name or a context from the library. Check if there is a method to get the correct package name from the library's resources. The fix likely involves modifying the call to `getIdentifier` to use the plugin's package name instead of the app's package name.