Question

我正在使用fragmentActivity for maps.In Java类在setContentView上获取错误。我的Mapscreen.java就像：它在某些设备上工作正常，只显示棉花糖崩溃。或者还有其他原因吗？

public class MapScreen extends FragmentActivity implements LocationListener,
GoogleApiClient.ConnectionCallbacks,
GoogleApiClient.OnConnectionFailedListener {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.map_screen);
    ....

    SupportMapFragment fm = (SupportMapFragment) getSupportFragmentManager()
            .findFragmentById(R.id.map);
    googleMap = fm.getMap();
}

    and my xml has fragment using SupportMapFragment as well. map_screen.xml is like :


    <?xml version="1.0" encoding="utf-8"?>
    <RelativeLayout 
      xmlns:android="http://schemas.android.com/apk/res/android"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:orientation="vertical" >

        <fragment
            android:id="@+id/map"
            android:name="com.google.android.gms.maps.SupportMapFragment"
            android:layout_width="fill_parent"
            android:layout_height="fill_parent"
            android:layout_alignParentLeft="true"
            android:layout_alignParentTop="true" />

        <ImageView
            android:id="@+id/startActivityButton"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_alignParentBottom="true"
            android:layout_centerHorizontal="true"
            android:layout_marginLeft="50dp"
           android:layout_marginRight="50dp"
            android:layout_marginBottom="44dp"
           android:background="@drawable/end_meetup_btn"
         />

    </RelativeLayout>

我无法找到相同的问题在Marshm 试图找到＆＃34;引起：java.lang.NullPoi

    12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026): 12-18 13:40:14.425: E/AndroidRuntime(8026):

Answer 1

问题出在＆＃34; Micro-max Android one mobile＆＃34;这是6.0棉花糖。此设备没有足够的内部或外部存储空间。即使没有SD卡。

从乔治中回答：

NullPointerException from Google maps

我安装了存储卡，现在崩溃了。

所以我发现问题是更新了Google Play服务，这些服务需要我的设备中不够的Space（更新后的Google照片）。

并且还有一个错误行显示＆＃34;引起：java.lang.NullPointerException：尝试调用虚方法＆＃39; boolean java.io.File.mkdir（）＆＃39;在null对象引用＆＃34;

我决定在安装SD卡后检查。它工作了

Answer 2

<!-- EXTERNAL_STORAGE permissions are optional for Android 6.0 onwards. -->
    <uses-permission
        android:name="android.permission.WRITE_EXTERNAL_STORAGE"
        android:maxSdkVersion="22" />
    <uses-permission
        android:name="android.permission.READ_EXTERNAL_STORAGE"
        android:maxSdkVersion="22" />

将此添加到您的清单中。也许地图需要sdcard权限才能获得一些额外的缓存或其他东西。

Answer 3

此问题已在Google Play服务库9.0.83版中修复。

Answer 4

这只是我做的一个解决方法。如果下面的检查失败，我加载了一个错误的片段，而不是加载地图。

/** Checks if external storage is available for read and write */
public boolean isExternalStorageWritable() {
    String state = Environment.getExternalStorageState();
    return Environment.MEDIA_MOUNTED.equals(state);
}

Answer 5

将SD卡权限添加到清单文件中。

    <uses-permission
    android:name="android.permission.WRITE_EXTERNAL_STORAGE"
     />

    <uses-permission
    android:name="android.permission.READ_EXTERNAL_STORAGE"
    />

地图的棉花糖碎片活动中的崩溃

5 个答案: