uni-app小程序中 uni.getLocation 查看地图返回后，出现“Error in nextTick: "TypeError: Cannot read property" 的错误

uni-app小程序中 uni.getLocation 查看地图返回后，出现“Error in nextTick: “TypeError: Cannot read property” 的错误

操作步骤：

小程序中 uni.getLocation 查看地图返回后，出现“[Vue warn]: Error in nextTick: “TypeError: Cannot read property ‘u1zp’ of null”” 的错误

预期结果：

无错误

实际结果：

小程序中 uni.getLocation 查看地图返回后，出现“[Vue warn]: Error in nextTick: “TypeError: Cannot read property ‘u1zp’ of null”” 的错误

bug描述：

小程序中 uni.getLocation 查看地图返回后，出现“[Vue warn]: Error in nextTick: “TypeError: Cannot read property ‘u1zp’ of null”” 的错误，但是整个项目中也没有代码会访问“u1zp”这个属性，完全找不到头绪。

具体错误信息

mp.runtime.esm.js?66fd:613 [Vue warn]: Error in nextTick: "TypeError: Cannot read property 'u1zp' of null"  
warn @ mp.runtime.esm.js?66fd:613  
Vue.config.errorHandler @ mp.runtime.esm.js?66fd:5816  
globalHandleError @ mp.runtime.esm.js?66fd:1878  
handleError @ mp.runtime.esm.js?66fd:1847  
(anonymous) @ mp.runtime.esm.js?66fd:1986  
flushCallbacks @ mp.runtime.esm.js?66fd:1912  
(anonymous) @ VM3721 WAService.js:2  
r @ VM3721 WAService.js:2  
Promise.then (async)  
a @ VM3721 WAService.js:2  
e.exports @ VM3721 WAService.js:2  
Z @ VM3721 WAService.js:2  
then @ VM3721 WAService.js:2  
timerFunc @ mp.runtime.esm.js?66fd:1939  
nextTick @ mp.runtime.esm.js?66fd:1994  
queueWatcher @ mp.runtime.esm.js?66fd:4342  
update @ mp.runtime.esm.js?66fd:4484  
notify @ mp.runtime.esm.js?66fd:727  
reactiveSetter @ mp.runtime.esm.js?66fd:1063  
proxySetter @ mp.runtime.esm.js?66fd:4571  
(anonymous) @ AppService.js:315  
fetchFromCache @ AppService.js:258  
fetchFromCacheForPage @ AppService.js:311  
fetchDetail @ Company.js:20  
onShow @ detail.vue:237  
invokeWithErrorHandling @ mp.runtime.esm.js?66fd:1862  
Vue.__call_hook @ mp.runtime.esm.js?66fd:5873  
_vue.default.__call_hook @ index.js?543d:1284  
mpOptions.&lt;computed&gt; @ index.js?543d:767  
(anonymous) @ VM3721 WAService.js:2  
r.__callPageLifeTime__ @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emitInternal @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emit @ VM3721 WAService.js:2  
v @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emit @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c @ VM8 asdebug.js:1  
l @ VM8 asdebug.js:1  
(anonymous) @ VM8 asdebug.js:1  
f @ VM8 asdebug.js:1  
g @ VM8 asdebug.js:1  
(anonymous) @ VM8 asdebug.js:1  
_ws.onmessage @ VM8 asdebug.js:1  

mp.runtime.esm.js?66fd:5817 TypeError: Cannot read property 'u1zp' of null  
at g (VM3721 WAService.js:2)  
at e.value (VM3721 WAService.js:2)  
at e.value (VM3721 WAService.js:2)  
at u._updateCb (VM3721 WAService.js:2)  
at u.doUpdates (VM3721 WAService.js:2)  
at a.m.setData (VM3721 WAService.js:2)  
at vt.&lt;anonymous&gt; (VM3721 WAService.js:2)  
at VueComponent.patch [as __patch__] (mp.runtime.esm.js?66fd:5649)  
at VueComponent.Vue._update (mp.runtime.esm.js?66fd:3959)  
at VueComponent.updateComponent (mp.runtime.esm.js?66fd:5700)  
Vue.config.errorHandler @ mp.runtime.esm.js?66fd:5817  
globalHandleError @ mp.runtime.esm.js?66fd:1878  
handleError @ mp.runtime.esm.js?66fd:1847  
(anonymous) @ mp.runtime.esm.js?66fd:1986  
flushCallbacks @ mp.runtime.esm.js?66fd:1912  
(anonymous) @ VM3721 WAService.js:2  
r @ VM3721 WAService.js:2  
Promise.then (async)  
a @ VM3721 WAService.js:2  
e.exports @ VM3721 WAService.js:2  
Z @ VM3721 WAService.js:2  
then @ VM3721 WAService.js:2  
timerFunc @ mp.runtime.esm.js?66fd:1939  
nextTick @ mp.runtime.esm.js?66fd:1994  
queueWatcher @ mp.runtime.esm.js?66fd:4342  
update @ mp.runtime.esm.js?66fd:4484  
notify @ mp.runtime.esm.js?66fd:727  
reactiveSetter @ mp.runtime.esm.js?66fd:1063  
proxySetter @ mp.runtime.esm.js?66fd:4571  
(anonymous) @ AppService.js:315  
fetchFromCache @ AppService.js:258  
fetchFromCacheForPage @ AppService.js:311  
fetchDetail @ Company.js:20  
onShow @ detail.vue:237  
invokeWithErrorHandling @ mp.runtime.esm.js?66fd:1862  
Vue.__call_hook @ mp.runtime.esm.js?66fd:5873  
_vue.default.__call_hook @ index.js?543d:1284  
mpOptions.&lt;computed&gt; @ index.js?543d:767  
(anonymous) @ VM3721 WAService.js:2  
r.__callPageLifeTime__ @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emitInternal @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emit @ VM3721 WAService.js:2  
v @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c.emit @ VM3721 WAService.js:2  
emit @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
(anonymous) @ VM3721 WAService.js:2  
c @ VM8 asdebug.js:1  
l @ VM8 asdebug.js:1  
(anonymous) @ VM8 asdebug.js:1  
f @ VM8 asdebug.js:1  
g @ VM8 asdebug.js:1  
(anonymous) @ VM8 asdebug.js:1  
_ws.onmessage @ VM8 asdebug.js:1

更多关于uni-app小程序中 uni.getLocation 查看地图返回后，出现“Error in nextTick: "TypeError: Cannot read property" 的错误的实战教程也可以访问 https://www.itying.com/category-93-b0.html

yibo5220 1楼

这个错误通常是由于uni-app小程序在页面切换或组件更新时，数据状态不一致导致的。u1zp是框架内部生成的属性名，错误提示表明在访问一个null对象的属性。

问题出现在从地图页面返回后触发nextTick更新时。可能的原因包括：

异步数据竞争：uni.getLocation是异步操作，返回页面时可能数据还未完全加载，导致模板中绑定的数据为null
组件生命周期问题：页面返回时，某些组件可能已经被销毁但仍在尝试更新
数据响应式问题：在onShow中直接修改响应式数据可能触发不完整的更新

解决方案：

检查detail.vue的onShow方法（第237行）和相关的数据初始化。确保在访问数据属性前进行空值检查：

onShow() {
  // 确保数据已初始化
  if (!this.someData) {
    this.someData = {}
  }
  this.fetchDetail()
}

同时检查模板中所有数据绑定，添加可选链操作符或空值判断：

<!-- 将 -->
<view>{{ data.u1zp }}</view>
<!-- 改为 -->
<view>{{ data?.u1zp }}</view>